FireFingers21

@Stephen_C You're so close! Changing the -name flag of the find command to -iname makes the match case insensitive, so this command should work for you:
 
 

@xorq Most people use GitHub to share their workflows, see this blog post to help get you up and running: https://www.alfredapp.com/blog/guides-and-tutorials/share-workflow-on-github/
 
You should also check out this guide for documenting your workflow with some best practices for making it shareable: https://www.alfredapp.com/help/workflows/advanced/sharing-workflows/
 
Welcome to the community!

@andy4222 You can customize how you'd like your Large Type to appear either globally or on a per-workflow basis with the Large Type Output object. The documentation for both respectively:
 
https://www.alfredapp.com/help/features/large-type/
 
https://www.alfredapp.com/help/workflows/outputs/large-type/

@xorq Most people use GitHub to share their workflows, see this blog post to help get you up and running: https://www.alfredapp.com/blog/guides-and-tutorials/share-workflow-on-github/
 
You should also check out this guide for documenting your workflow with some best practices for making it shareable: https://www.alfredapp.com/help/workflows/advanced/sharing-workflows/
 
Welcome to the community!

@howdytom You could use an app like Menu Bar Dock. Adding Alfred to the "Regular Apps" list and setting the "Max Number of Running Apps" slider to 0 will mimick the one-click behaviour of the Spotlight Menu Bar module. Alfred doesn't have this built in, as its Menu Bar module requires two clicks.
 
Although to really take advantage of the benefits and capabilities of Alfred, your friend should probably try training a hotkey to muscle memory. A lot of people just like to remap Spotlight's default ⌘+Space hotkey to activate Alfred instead. Since Alfred is a text-based app, activating it from the keyboard is a lot faster than using your mouse/trackpad to find and click a button on the screen.

@rob213 See this blog post: https://www.alfredapp.com/blog/tips-and-tricks/search-automation-tasks-in-workflows/

@Floating.Point The JSON Utility is caching the initial value of the split2 variable, as you discovered when modifying the workflow causing a reload. I don't ever use that object, so I don't know why it only lets you modify the "script" config once.
 
That said, you're probably looking for the eval command, which lets you execute arguments as a shell command. Try removing the Arg and Vars and JSON Utility objects and just go straight into the Run Script, then set the script within to eval $split2. Your test workflow should work as intended.

Well, developing my previous idea a little you could use a single, memorable keyboard shortcut, for example, to clear the search field in multiple apps—detecting the relevant app and then applying the relevant sequence of keystrokes in that detected app. In other words, the Automation Task would detect the app with focus and the conditional would lead to application of the relevant sequence of keystrokes for that app. All you'd need to recall is that the ⌃⌥⌘C hotkey clears a search field.
 
OK, I'm desperate for redemption…and it's only an idea. 😀
 
Stephen

Oh no!😅 At least a learning opportunity was still had. I await your redemption post, whenever the next instalment of Simple Ideas may be!

Background
Do you sometimes want to restrict an Alfred hotkey to work only in one app and not in others? For example, you might want to use Alfred’s Dispatch Key Combo Output to send keystrokes to a specific app but not to any other app. There’s an easy way to do that.

The skeletal workflow
I’ve included this workflow merely as an example. I use it to clear, with a single keystroke, DEVONthink searches and return the focus to the group (in the sidebar) in which the search was made. However, the specifics are not as important as the basic technique.


Explanation
We start with Alfred’s Hotkey Trigger and set our hotkey. That is linked to an Automation Task to identify the front app (i.e., the app with focus) and to output the name.

We use Alfred’s Conditional Utility to check that the app in which we wish to use the hotkey has focus. The inner workings of the Conditional Utility (revealed by double-clicking on it) are simple and look like this:


The result is also simple: unless the output from the Conditional Utility is, in this case, DEVONthink 3 the workflow quits.

All we then need to do is to send to DEVONthink, using Alfred’s Dispatch Key Combo Outputs the sequence of keystrokes we wish to use. Note that we sometimes have to include short Delays in the sequence in order to make it work effectively.

In conclusion
None of this is sophisticated but it’s a good way to use Alfred to automate something in a specific app when you wish to limit your Alfred hotkey to affecting only that app.

Stephen

The Simple Ideas posts

@matthewmcvickar It's the way you're encoding the square brackets around "keyword". They should be encoded too, not just the spaces. Leave the encode spaces setting to its default of "%20", and your Search URL should look like this:
 
https://boomkat.com/products?q%5Bkeywords%5D={query}

@ken luu It's not an Alfred feature, it's an Apple feature of macOS and iOS called Universal links. It lets developers associate web links with a particular app. Another example you may have already seen is with App Store and iTunes links. You'll notice if you try to open the App Store page for TickTick (https://apps.apple.com/ca/app/ticktick-to-do-list-calendar/id966085870?mt=12), it opens directly in the App Store rather than your browser. Or if you do paste that link directly in your browser, you'll see a popup asking if you'd like to open the link with the App Store.
 
Universal links and URL Schemes are both ways for apps to handle content rather than having the OS only load the link in a web browser.

@e2o You can accomplish this using a workflow with a Hotkey going into a Dispatch Key Combo Output. You'll first have to temporarily delete the Viewer Hotkey in the Clipboard History settings, then add it to the Hotkey object in the workflow (I would also recommend changing the trigger behaviour to "Pass through modifier keys", otherwise you'll notice a bit of lag). Once the workflow hotkey is programmed, you can add back the Viewer Hotkey in Clipboard History settings. Then go back to the workflow and set the Dispatch Key Combo to output a down arrow.
 
Now when you use your hotkey to view Alfred's Clipboard History, pressing it again will move you down the list instead of making it disappear.

@gedeyenite You can find your current Desktop Space by looking at the "com.apple.spaces" plist. It's located at "~/Library/Preferences/com.apple.spaces.plist", but you can read it from Terminal or a shell script using the "defaults read com.apple.spaces" command.
 
Each Space has a name/uuid (they're one in the same). There's a "Current Space" field that contains the uuid of the current Space, and a "Space Properties" field that contains the name of all the Spaces currently available. If you can figure out a script that matches the "Current Space" uuid with that of whichever Space your app is in, you should have a good basis for the workflow you're trying to accomplish.

Most existing workflows for performing a WHOIS lookup seem to be search wrappers for specific websites. Between the limitations of different sites and the degree of trust needed to use them, a more robust option seemed necessary. As such, I've created a workflow that performs WHOIS lookups with no external dependencies. Supporting both domains and IP addresses, it's powered by the built-in "whois" shell command and makes use of Alfred 5.5's new Text View! What's more, a text file can also be generated for extended viewability and searchability of data.
 
⤓ Download | Source
 
WHOIS Lookup
 
Usage

Perform a WHOIS lookup using the whois keyword. Type the domain or IP address you would like to query.


↩: View WHOIS data in Alfred’s Text View ⌘↩: View raw WHOIS data in a text file
The Text View will try to summarize important information at the top, then display the raw, unmodified data at the bottom. You can choose which information you’d like summarized in the Workflow’s Configuration.

Configure the Hotkey as a shortcut to perform a WHOIS lookup. Use the Universal Action to query URLs from Alfred’s Clipboard History or selected text.

Most existing workflows for performing a WHOIS lookup seem to be search wrappers for specific websites. Between the limitations of different sites and the degree of trust needed to use them, a more robust option seemed necessary. As such, I've created a workflow that performs WHOIS lookups with no external dependencies. Supporting both domains and IP addresses, it's powered by the built-in "whois" shell command and makes use of Alfred 5.5's new Text View! What's more, a text file can also be generated for extended viewability and searchability of data.
 
⤓ Download | Source
 
WHOIS Lookup
 
Usage

Perform a WHOIS lookup using the whois keyword. Type the domain or IP address you would like to query.


↩: View WHOIS data in Alfred’s Text View ⌘↩: View raw WHOIS data in a text file
The Text View will try to summarize important information at the top, then display the raw, unmodified data at the bottom. You can choose which information you’d like summarized in the Workflow’s Configuration.

Configure the Hotkey as a shortcut to perform a WHOIS lookup. Use the Universal Action to query URLs from Alfred’s Clipboard History or selected text.

Incidentally, I actually started a workflow just a few weeks ago for performing WHOIS lookups which I eventually plan to share. It uses the built-in "whois" shell command and nicely formats the data into Markdown for viewing with Alfred's Text View. Currently, it's got a toggleable summary at the top with all the raw WHOIS data at the bottom. The summary includes basic domain and contact information and automatically excludes redacted data. Here's a screenshot of the markdown it currently generates, let me know if you have any feedback on the summary and any other functional features you think the workflow should have:

Incidentally, I actually started a workflow just a few weeks ago for performing WHOIS lookups which I eventually plan to share. It uses the built-in "whois" shell command and nicely formats the data into Markdown for viewing with Alfred's Text View. Currently, it's got a toggleable summary at the top with all the raw WHOIS data at the bottom. The summary includes basic domain and contact information and automatically excludes redacted data. Here's a screenshot of the markdown it currently generates, let me know if you have any feedback on the summary and any other functional features you think the workflow should have:

Incidentally, I actually started a workflow just a few weeks ago for performing WHOIS lookups which I eventually plan to share. It uses the built-in "whois" shell command and nicely formats the data into Markdown for viewing with Alfred's Text View. Currently, it's got a toggleable summary at the top with all the raw WHOIS data at the bottom. The summary includes basic domain and contact information and automatically excludes redacted data. Here's a screenshot of the markdown it currently generates, let me know if you have any feedback on the summary and any other functional features you think the workflow should have:

@gedeyenite You can find your current Desktop Space by looking at the "com.apple.spaces" plist. It's located at "~/Library/Preferences/com.apple.spaces.plist", but you can read it from Terminal or a shell script using the "defaults read com.apple.spaces" command.
 
Each Space has a name/uuid (they're one in the same). There's a "Current Space" field that contains the uuid of the current Space, and a "Space Properties" field that contains the name of all the Spaces currently available. If you can figure out a script that matches the "Current Space" uuid with that of whichever Space your app is in, you should have a good basis for the workflow you're trying to accomplish.

@FireFingers21 many thanks for the suggestion. Shell script has never been my forte and your idea is very much better, and more easily adaptable, than my original. I'll release an update later in the day…at a slightly more civilised UK time than now. 😀 Thanks again.
 
Stephen

This looks awesome! I have a few suggestions for streamlining the use of exclusions.
 
In both Arg and Vars objects, you could rename the variables from "searchTerm" to "fuzzyTerm" and "verbatimTerm" respectively. Then in the Run Script object for assembling the URL, you could adjust the code to look something like this:
exclusions='' # Add exclusions here [ "${exAmazon}" -eq 1 ] && exclusions+=' -Amazon' [ "${exeBay}" -eq 1 ] && exclusions+=' -eBay' [ "${exYouTube}" -eq 1 ] && exclusions+=' -YouTube' # Assembly of fuzzy or verbatim search URL taking account of exclusions if [ -n "${fuzzyTerm}" ]; then echo "${theHost}search?q=${fuzzyTerm}+$exclusions &udm=14" else echo "${theHost}search?q=${verbatimTerm}+$exclusions &udm=14&tbs=li:1" fi  
By setting the fuzzy and verbatim search variables to different names, we only need a single Run Script rather than two. Also instead of creating a new variable for each exclusion, the code above starts with an empty string and adds each exclusion automatically, eliminating the need for step 5 in your documentation. This also allows for simplified if statements, as an "else" clause is no longer required. You can still use a normal if statement if you prefer, but these one-liners can accomplish the same thing with less code to worry about.