Jump to content

Search the Community

Showing results for tags 'symlink'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Alfred 3
  • Make the Most of Alfred
    • Discussion & Help
    • Bug Reports
    • Alfred Feature Suggestions
    • Themes
  • Alfred Workflows
    • Share your Workflows
    • Workflow Help & Questions
  • Alfred v2 Themes
  • Alfred Remote for iOS
    • Alfred Remote Discussion & Help
    • Remote Connection Troubleshooting

Categories

  • Articles
    • Forum Integration
    • Frontpage
  • Pages
  • Miscellaneous
    • Databases
    • Templates
    • Media

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Twitter


Website URL


Jabber


Location


Interests

Found 5 results

  1. Affected Alfred version: Every version of Alfred 3 Alfred 3 refuses to export workflows that are symlinked to its workflow directory with a "working directory doesn't exist" error.
  2. I just finished setting up my new install of Yosemite, except for my hotkeys. I decided to use homebrew-cask to install a bunch of my apps this time around, which actually installs the apps to /opt/homebrew-cask/Caskroom/ and symlinks them into ~/Applications. While my hotkeys are successfully switching between apps, "Toggle visibility for apps" doesn't seem to be working. It does work on my other apps that were installed through the App store, just not with those being symlinked. I've tried with all of the different trigger behaviors and it doesn't seem to help. I'm using the latest Yosemite and Alfred v2.5 (299).
  3. Right now things like homebrew make symbolic links in the /Applications (or ~/Applications) folder to somewhere like /usr/local/Cellar/<package>/<version>/<Appname>.app. Now I have to go in manually to remove the symlink (public.symlink) and replace it with a finder alias (com.apple.alias-file). Other people in the bug forum just add the Cellar path to Alfred every time the version changes (way less than ideal). Alfred ignores symlinks in the Applications folders even after adding them to the "User-defined" file types in Default Results | Advanced. It allows com.apple.alias-file types however.
  4. I've been developing my first few workflows, and I'm following a development model that looks like: - Have a git repo somewhere on my local machine that's pushed to github. - Symlink that directory into the Alfred workflow preferences folder - Alfred workflow preferences is under Dropbox, so it syncs between machines. A few questions have come up as I get deeper into this. 1. When I do an export of a workflow in Alfred preferences, so I can share the latest version with the world, does that package up the entire directory? Meaning, all the .git directories, project history, etc? 2. Is this symlink model the preferred way to handle things? Or do experienced devs find it's better to write a script to "install" a workflow standalone, because it causes less conflicts and problems. (one example is that Alleyoop won't find equipped workflows if they are symlinked, but I suspect other issues might arise with workflows or Alfred itself) (update: Alleyoop 2.552 and above now respects symlinked directories) Any other tips from experienced developers on git-managed workflows?
  5. Workflow to create a symbolic link to a designated file or directory. The file/directory to link against is designated by typing the keyword ”sym” followed by the item’s path in the Alfred dialog box, or by first selecting the item in the Finder and then using Alfred’s built-in Finder Selection action menu. The new symbolic link is saved to the Desktop by default. Download Symbolic Link Creator or clone repo from GitHub: github.com/Morse-Code/Alfred - Chris
×
×
  • Create New...