vdesabou Posted October 26, 2016 Share Posted October 26, 2016 Hi Team, I've noticed this: -Install Getting Started Workflow Variables workflow -Move the workflow directory to Downloads directory for example -Do a symlink: Example: MacBookPro-Vincent:[12:39:14]/Users/vdesabou/Dropbox/Alfred.alfredpreferences/workflows> ln -s /Users/vdesabou/Downloads/user.workflow.7D127576-3643-442A-896D-46794F2058EA testkeyword -Eventually restart alfred and alfred preferences After that, all modifications to keyword variables are ignored. So for example if I set "ttt" as variable, it does not work. I have latest version of Alfred 3. It was working before, but somehow got broken after an update, but I can't tell you which one. Thanks Link to comment Share on other sites More sharing options...
Andrew Posted October 26, 2016 Share Posted October 26, 2016 I can see why this is possibly happening as Alfred doesn't fully resolve symlinks before writing the info.plist, but I'm not sure why this would have worked before but not now. Either way, I'll fix this for the next release Cheers, Andrew Link to comment Share on other sites More sharing options...
vdesabou Posted October 26, 2016 Author Share Posted October 26, 2016 12 minutes ago, Andrew said: I can see why this is possibly happening as Alfred doesn't fully resolve symlinks before writing the info.plist, but I'm not sure why this would have worked before but not now. I'm pretty sure because I added the possibility to rename all commands for the Spotify Mini Player workflow on June 30th (https://github.com/vdesabou/alfred-spotify-mini-player/issues/132), and I've always worked in a symlinked manner for this workflow. So I'm pretty sure that it worked with Alfred 3.0.2 12 minutes ago, Andrew said: Either way, I'll fix this for the next release Nice !! Thanks ! Link to comment Share on other sites More sharing options...
deanishe Posted October 26, 2016 Share Posted October 26, 2016 (edited) Funny. I'm not seeing this at all, and almost all of my workflows are symlinked. Alfred 3 definitely has more issues with symlinks than v2 did, however, like failing to export symlinked workflows. Edited October 26, 2016 by deanishe Link to comment Share on other sites More sharing options...
Andrew Posted October 27, 2016 Share Posted October 27, 2016 The 3.2 pre-release should fix this - could you let me know how you get on Link to comment Share on other sites More sharing options...
vdesabou Posted October 27, 2016 Author Share Posted October 27, 2016 11 minutes ago, Andrew said: The 3.2 pre-release should fix this - could you let me know how you get on Yes, I confirm it fixes the problem on my side ! Thanks ! Link to comment Share on other sites More sharing options...
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