deanishe

Not that URL, no. You can clearly see it's a Devon Think-specific URL. If you want to open the item in PDF Expert, you will presumably need the path to the corresponding PDF file, not just the Devon Think item ID.

Those aren't hotkeys, that's part of macOS's text input system. You can't bind key combinations like that in text input fields because it breaks text entry.

This shell command opens a new Firefox window: /Applications/Firefox.app/Contents/MacOS/firefox-bin --browser

Here's a modified version that opens the URL when you press ⌘↩. You can see quite clearly what I've added.

Hi @csmm, welcome to the forum. Alfred won't automatically open the files for you: by design, it doesn't do anything unless the user specifically tells it to. You could create a File Filter that shows ZIP and DMG files in ~/Downloads, sorted by date, and connect that to an Open File action. Check out the Simple Folder Search example workflow (go to Workflows in Alfred Preferences and press the + button at the bottom).

You don't need to: if you leave out the date entirely, it defaults to the current date. https://www.visa.com.au/travel-with-visa/exchange-rate-calculator.html?fromCurr=USD&toCurr=AUD&fee=0&utcConvertedDate=&submitButton=Calculate+Exchange+Rates

Yeah. Actually running workflows is completely out of the question because of the side effects. It might be possible for Alfred to also interpolate static values from info.plist/the config sheet when it’s compiling its help data. I have no idea how feasible that is architecturally. It does already read those variables when loading a workflow because you can use {var:...} in Keyword fields, too. Yeah, it does look odd. It also means that you can't find workflows by keyword if the keyword is set via a variable. As far as help is concerned, it’s {var:keyword}. This isn't very common, however, and there's no reason to do it at all any more.

Alfred 4 supports macOS 10.11 and above. It seems unlikely that Andrew will replace the mini player with something that only works on Monterey.

@Damoeire: Check out this thread (it's probably relevant to your problem):

Depends how you look at it, I suppose. You're effectively running the "Alfred help" workflow, and it doesn't set those variables, so there are no values to use. I’m not sure it’s tenable to populate the variables from their source workflows in help mode because Alfred would potentially have to bootstrap all your workflows every time you run the help, which might absolutely murder performance. This is mostly just a guess (only Andrew knows how Alfred actually works), but Alfred doesn't load workflows the way other programs load plugins (i.e. bootstrap and load everything on program start, and have it all in memory ready to go). It's more like your shell, where it knows what keywords/commands exist, but workflow's aren't loaded or running in any meaningful sense until you actually execute one. That way, Alfred's start-up time and RAM usage don't balloon as you install more workflows. Alfred's performance and resource usage remain basically the same, regardless of whether you have 10 workflows or 1000.

Glad you got it working 👍

I totally agree with that. It’s ⌘F focussing a different field dependent on context in the same view that I think is somewhat questionable. It should be a different shortcut, imo, say ⇧⌘F.

Why would that be better than Search Preferences?

You could grab ShortcutDetective from this page (it's free). Make sure KM and Alfred are both running, start ShortcutDetective, then use Alfred's selection hotkey. ShortcutDetective should be able to tell you which application received the keypress.

Sorry, I don't know then. I have no idea how Alfred works internally, and I don't have macOS 11. Perhaps @Andrew can shed some light.