-
-
Notifications
You must be signed in to change notification settings - Fork 10.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Programmatically modify Alfred scope #18
Comments
Great idea! Going to build this in soon - maybe a 'brew cask linkalfred' command. Probably no harm in programmatically bouncing Alfred for you while we're at it, eh? Will investigate this when testing. |
But be sure not to hardcode "/usr/local/Cellar", as some people use another directory (I'm assuming homebrew can be queried for it's prefix). |
Good call @autodidakto. Hoping to pick this up this weekend and I'll keep that in mind. On Tuesday, October 9, 2012 at 3:21 PM, autodidakto wrote:
|
Months later, this is finally done! 📆 |
Does this work for you with Alfred 2? I'm currently running v2.0.3 (187), and it doesn't seem to have a "scope.paths" key in the com.alfredapp.Alfred plist file. I tried adding it with:
But that didn't seem to affect the search scope, even after restarting Alfred. I feel like I'm missing something obvious here. |
No you're probably right. I developed this feature on Alfred 1.x and just crossed my fingers that the preferences were forwards compatible. ;) I'll finally upgrade and get this fixed up |
I've updated everything I can think of:
Any ideas? |
I hadn't cut a release yet with this fix in - so you would have had to be tracking HEAD in order to get the fix. I just cut |
No dice.
This isn't a blocker for me as I've already added the folder to Alfred. However, it seems like it should be removed from |
PEBKAC All is well after
|
You could have an option to programmatically edit the Alfred scope by doing the following:
NB: I don't know how to make Alfred see this change without restarting Alfred.
The text was updated successfully, but these errors were encountered: