Ryan McGeary Posted January 12, 2018 Share Posted January 12, 2018 (edited) When upgrading a workflow, if "Migrate my settings" is checked, settings such as custom keyword inputs and custom hotkeys are kept; however, if a keyword is customized and the associated "with space" setting is also customized, the "with space" setting is not migrated during the upgrade. I expected that the "with space" setting would migrate just like the keyword migrates. As an example, when I upgrade Alfred Emoji, I change my keyword from "emoji" to to a single character (:), but I also uncheck the "with space" setting, because I want to emulate emoji completion in tools like GitHub or Slack. Alfred version & build number: v3.5.1 [883] OS X version: 10.13.2 (17C205) Edited January 12, 2018 by Ryan McGeary Link to comment Share on other sites More sharing options...
deanishe Posted January 12, 2018 Share Posted January 12, 2018 1 hour ago, Ryan McGeary said: I want to emulate emoji completion in tools like GitHub or Slack. That's the great thing about your workflow: it uses the same names as GitHub. Where do the names come from, exactly? I have a couple of other emoji-supporting workflows, like Dash or my own Unicode one, but they use the official Unicode names, like SMILING FACE WITH OPEN MOUTH AND COLD SWEAT, instead of the much handier sweat_smile. Link to comment Share on other sites More sharing options...
Ryan McGeary Posted January 13, 2018 Author Share Posted January 13, 2018 43 minutes ago, deanishe said: That's the great thing about your workflow: it uses the same names as GitHub. Where do the names come from, exactly? From the Emoji keyword library: https://github.com/muan/emojilib deanishe 1 Link to comment Share on other sites More sharing options...
deanishe Posted January 13, 2018 Share Posted January 13, 2018 (edited) Awesome. That looks very handy. Thanks very much. This is the first I've heard of the Fitzpatrick scale, and I must say I'm a bit peeved that they think us Brits are the pastiest-faced of them all ? Edited January 13, 2018 by deanishe Link to comment Share on other sites More sharing options...
Ryan McGeary Posted January 22, 2018 Author Share Posted January 22, 2018 Could someone please confirm that what I perceived as a bug is actually considered a bug? /cc @Vero @Andrew Link to comment Share on other sites More sharing options...
Andrew Posted January 22, 2018 Share Posted January 22, 2018 @Ryan McGeary this'll be fixed in the next pre-release. Not a bug per-se, but I thinking about this, it's close enough related to the keyword that it should be migrated too. Ryan McGeary 1 Link to comment Share on other sites More sharing options...
Andrew Posted January 24, 2018 Share Posted January 24, 2018 @Ryan McGeary this should now be fixed in the 3.6 b893 pre-release Ryan McGeary 1 Link to comment Share on other sites More sharing options...
Ryan McGeary Posted January 24, 2018 Author Share Posted January 24, 2018 3 hours ago, Andrew said: this should now be fixed in the 3.6 b893 pre-release Brilliant. I just tried it. It worked great! Thank you! 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