alexreg Posted September 23, 2016 Share Posted September 23, 2016 For some reason, Alfred 2 seems to be running in the background even when Alfred 3 is running. (Alfred 2 is not a startup item for my user, I double checked.) I notice this when I quit Alfred 3 and restart it (e.g. for an update), and it complains Alfred 2 is running. What's up with this? Link to comment
vitor Posted September 24, 2016 Share Posted September 24, 2016 Before thinking of anything else, why do you still keep Alfred 2 around in your system? Can’t you just delete it? Link to comment
Vero Posted September 27, 2016 Share Posted September 27, 2016 @alexreg I would guess that you're seeing this because you have a workflow that has a hard-coded reference to Alfred 2, causing it to be launched inadvertently. Check your workflows, as most will have more current Alfred 3 versions if created by other users. If they're your own workflows, you'll need to update the references. Cheers, Vero Link to comment
alexreg Posted September 27, 2016 Author Share Posted September 27, 2016 2 hours ago, Vero said: @alexreg I would guess that you're seeing this because you have a workflow that has a hard-coded reference to Alfred 2, causing it to be launched inadvertently. Check your workflows, as most will have more current Alfred 3 versions if created by other users. If they're your own workflows, you'll need to update the references. Cheers, Vero Thanks for the reply. Any for an easy way to check for hard-coded references? I have a number of workflows, so no idea just scanning them which might be the culprit! Link to comment
steyep Posted September 27, 2016 Share Posted September 27, 2016 3 hours ago, alexreg said: Any for an easy way to check for hard-coded references? I have a number of workflows, so no idea just scanning them which might be the culprit! How about this? workflows="$HOME/Dropbox/Alfred.alfredpreferences/workflows" # Path to your workflows find $workflows -type f -exec sh -c 'grep -q "Alfred 2" "$0" && echo "$0"' "{}" \; You can run this in the terminal to return a list of files containing the string "Alfred 2" alexreg 1 Link to comment
deanishe Posted September 27, 2016 Share Posted September 27, 2016 I think grep -R 'Alfred 2' /path/to/workflows would be enough. alexreg 1 Link to comment
steyep Posted September 27, 2016 Share Posted September 27, 2016 1 hour ago, deanishe said: I think grep -R 'Alfred 2' /path/to/workflows would be enough. Yes. Or that much more concise solution Link to comment
vitor Posted September 27, 2016 Share Posted September 27, 2016 greping will likely yield unsatisfactory results. I thought to suggest that but ran the command in my own workflows directory first, and the results were really unhelpful. Most of the results were from frameworks the workflows themselves use, which are just noise in trying to diagnose the cause. A more efficient way would be to just delete Alfred 2 from the system (@alexreg hasn’t said why he still keeps Alfred 2). Particularly if they can’t run at the same time and he seems to only run Alfred 3 on purpose, I don’t see the reasoning to keep them both (and this problem) around. Link to comment
deanishe Posted September 27, 2016 Share Posted September 27, 2016 (edited) 1 hour ago, vitor said: greping will likely yield unsatisfactory results. I thought to suggest that but ran the command in my own workflows directory first. The results are far from great, but all in all, it's still a damn sight better than going through all your workflows by hand… 1 hour ago, vitor said: A more efficient way would be to just delete Alfred 2 from the system (@alexreg hasn’t said why he still keeps Alfred 2). Particularly if they can’t run at the same time and he seems to only run Alfred 3 on purpose, I don’t see the reasoning to keep them both (and this problem) around. Oh definitely. Especially as the "offending" workflows would immediately throw errors (well, fail silently, as is the Alfred way…). I figured that @alexreg perhaps has a good reason for keeping Alfred 2 around (I still have it installed in case I need to fix a bug in a workflow and don't want to break Alfred 2 support). Edited September 27, 2016 by deanishe I *hate* this editor Link to comment
alexreg Posted September 27, 2016 Author Share Posted September 27, 2016 (edited) Thanks for your suggestions guys. I kept Alfred 2 around for the same reason as @deanishe. I think the following yields more relevant results, after inspection: grep -R 'tell application "Alfred 2"' . I did a find/replace on this text, updating to Alfred 3, and all seems to be good. Edited September 27, 2016 by alexreg deanishe 1 Link to comment
deanishe Posted September 27, 2016 Share Posted September 27, 2016 4 minutes ago, alexreg said: grep -R 'tell application "Alfred 2"' . Very well thunk! Link to comment
vitor Posted September 27, 2016 Share Posted September 27, 2016 14 minutes ago, alexreg said: grep -R 'tell application "Alfred 2"' . Of course! Well done. Link to comment
alexreg Posted September 27, 2016 Author Share Posted September 27, 2016 Thanks for the pointers, guys. Link to comment
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now