David Moe Posted January 3 Share Posted January 3 (edited) Say if you’re the author or submitting someone else’s workflow. I'm the author Share a link to its thread on the Alfred Forum, if available. NA Share a link to its main page (e.g. GitHub). https://github.com/logicxd/alfred-vscodediff If it has dependencies, say what those are unless they are explicit in the About or README. Requires Visual Studio Code. Provide screenshots, unless valid ones are in the About or README. This is the same image as the one in README Edited January 3 by David Moe Add tags to categorize workflow Link to comment Share on other sites More sharing options...
vitor Posted January 3 Share Posted January 3 Welcome @David Moe, The workflow is using Workflow Environment Variable instead of Workflow Configuration. Though it doesn’t seem like it should need any configuration at all, seeing as they point to temporary files. An alternative approach would be to eschew the variables and write the files to the workflow’s cache. Link to comment Share on other sites More sharing options...
David Moe Posted January 4 Author Share Posted January 4 Thanks! Did not know about the cache, yeah that'll work. I've gone ahead and changed it to use the cache as well as set up the Workflow Configuration for the location to the Visual Studio Code executable in case people have a different location. Check it out at https://github.com/logicxd/alfred-vscodediff/releases/tag/1.3.1-beta Link to comment Share on other sites More sharing options...
vitor Posted January 4 Share Posted January 4 Looks like you forgot to attach the packaged workflow to the release. Link to comment Share on other sites More sharing options...
David Moe Posted January 4 Author Share Posted January 4 Whoops, uploaded now. Link to comment Share on other sites More sharing options...
vitor Posted January 4 Share Posted January 4 That is a nice improvement. There’s another one you can make in that vein: Instead of three Keyword Inputs, have a single one. In the Workflow’s Configuration, add another text field for the keyword and use the variable as the value in the Kewyord Input. The documentation explains how that’s done. Here’s the workflow with the changes (I’d submit a PR, but the contents aren’t in the GitHub repo). I’ve also made made a small tweak to call the current configuration “VSCode CLI” and quoted the vscode variable (otherwise spaces in the path would trip up your code). Link to comment Share on other sites More sharing options...
David Moe Posted January 6 Author Share Posted January 6 All those changes sounds good to me! I've made it as a 1.3.2 release https://github.com/logicxd/alfred-vscodediff/releases/tag/1.3.2-beta Feel free to make a PR and add the Workflow to the GitHub repo for credit Link to comment Share on other sites More sharing options...
vitor Posted January 6 Share Posted January 6 1 hour ago, David Moe said: Feel free to make a PR and add the Workflow to the GitHub repo for credit Not necessary, I’m satisfied with having the changes in. But thank you, and for the quick changes. This will be in soon at http://alfred.app/workflows/logicxd/vscodediff/ Link to comment Share on other sites More sharing options...
xilopaint Posted April 18 Share Posted April 18 @David MoeThanks for this simple and useful workflow. Any reason for using /usr/local/bin/code as the default path of the CLI instead of just using code, which would make it work for Homebrew installations in both ARM and Intel Macs? Link to comment Share on other sites More sharing options...
David Moe Posted April 18 Author Share Posted April 18 (edited) @xilopaint no specific reason, I just didn't consider Intel Macs. I'll update the workflow on my GitHub, not sure what the process is for updating on Alfred Gallery. Thanks for the feedback! Edited April 18 by David Moe Link to comment Share on other sites More sharing options...
Stephen_C Posted April 18 Share Posted April 18 38 minutes ago, David Moe said: not sure what the process is for updating on Alfred Gallery If you make a new release on GitHub it will be picked up by the Gallery—which will update automatically after a short delay (just to allow for any small fixes to the new release). Stephen David Moe 1 Link to comment Share on other sites More sharing options...
xilopaint Posted April 18 Share Posted April 18 2 hours ago, David Moe said: @xilopaint no specific reason, I just didn't consider Intel Macs. I'll update the workflow on my GitHub, not sure what the process is for updating on Alfred Gallery. Thanks for the feedback! Actually, /usr/local/bin is more commonly used on Intel Macs than on ARM. If you install VS Code by Homebrew in an ARM Mac, for example, the binary will be placed in /opt/homebrew/bin. 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