luckman212

@Andrew Haha. Figures it would be me.

Thanks for looking. I swapped in an ArgsVars object instead and that works.

From https://www.alfredapp.com/help/workflows/advanced/placeholders/#modifiers

I am trying to use things like {query.stripnonalphanumeric} but I only get the raw text output... are the Transform Modifiers not supported in the Workflow JSON object?

Hmm that's (good) news to me! I tried putting {var:foo} in the AT configuration panel and it didn't work. Maybe I did something wrong, I will try again. Also, it's not mentioned in the docs that variables are supported...

edit: Hmmph. I just tried it again and yes, it works fine. Not sure what was going on earlier!

Quote

you're a much more advanced programmer

doubtful ! 🙃

still, I don't think the Automation Tasks can reference variables (yet) either.

https://www.alfredapp.com/help/workflows/utilities/file/

Would be very useful to support variables for the file(s) to check, instead of having to swap around arg/query to use this object...

Thanks @vitor I had a play and think I grasp it now. So when actioning an item via <TAB> key from a Script filter, the "action": { ... } will override the value passed into the remainder of the workflow, overriding the arg key. And, some detection is done to see if it's text, file(s) or url. Is this correct?

Still unclear to me whether it makes sense to have multiple types defined e.g.

"action": {
  "text": "one",
  "auto": "two"
}

In that case, if the arg was a string abc would the output be one or two ? 

Is there a way to determine which format was autodetected further downstream in the script via some variable?

Thanks. I will have a look at those.

I was re-reading https://www.alfredapp.com/help/workflows/inputs/script-filter/json/ today checking for recent changes that were introduced in 5.5. I noticed that there's an "action" key (apparently not new...) that can be used to customize the behavior when used with Universal Actions. I might be having a "slow brain" day, but I can't quite wrap my head around how this works or when it would be useful. 

Anyone got any examples (real world or hypothetical) of this feature?

v2.5.0 has more actions that can be called from the Grid View (integrated with CleanShot), allows multi-select via File Buffer, and some additional Workflow configuration options as well such as Grid Size and trigger keyword.

https://github.com/luckman212/alfred_clipsaver_workflow/releases/tag/2.5.0

Great stuff Vitor! Thank you as always. I've pushed a 2.5.0 update jist now that makes use of both of these!

I had my first play with Grid View yesterday and it's very slick! 🏆

I have a few suggestions if you'll hear them:

• I know about ⌘0 but it would be fantastic if ⌘+ and ⌘- could "resize" the grid, increasing or decreasing the size of the thumbnails. 
• Dovetailing with that, a way to programmatically set the grid size via JSON or workflow variable would be lovely to have
• And finally my "reach" request (I know it's a big one) - Multi-Select (similar to the way fzf works if you've ever used it). TAB key to mark/unmark an item and then ENTER to pass all selected objects to the output.

Thanks for this workflow @vitor

I hope you don't mind but I borrowed (stole?) your sqlite3 command to output the JSON for my grid view in the last version of my ClipSaver workflow.

I can no longer edit the top post, so just announcing here that I just pushed a small update (2.4.2) that supports Alfred 5.5's new Grid View.

https://github.com/luckman212/alfred_clipsaver_workflow/releases/tag/2.4.2

Reading the release notes now, wow a truly massive update! Thank you so much for this! Looking forward to diving in.

Holy crap. It works.

🤯

Is this a new feature (that arg can be an array)? I have been using Alfred for 7 years and never knew this.

Sorry, I haven't had my morning coffee yet but– I'm not following you Vitor. How can I output an array from my Script Filter?

@Binh Tran Not an exact answer to your question, but if you're looking for a way to "reveal" and/or save your captured clipboard images, you might give my ClipSaver workflow a try.

Was going to tack on to this 2 year old post, but found I couldn't. So, apologies for opening up a new thread, but I wanted to see if there'd been any further consideration of matching on multiple distinct kMDItemKeywords.

Can the https://www.alfredapp.com/help/workflows/utilities/split-arg/ workflow action be coerced into splitting on the NUL byte, a-la xargs -0?

When I try to pass a Script Filter's output with its arg set to a NUL-separated string, I get an error like this... 

Turns out the culprit for this bug appears to be macOS, not Alfred. I filed an FB ticket with Apple about it (related to PPPC permissions about ScreenCapture) so hopefully it won't make it all the way to the 14.4 release.

Thanks @Andrew I only noticed 1 thing so far, I'll report it over in the other forum, but it's more likely a macOS bug than an Alfred one anyway.

Just a friendly check in to see how things are cooking in Alfred's kitchen. We're approaching a short-term record for time between updates (last one was Dec '22 build 2110 → Apr '23 b2134) so I thought now might be an OK time to check in and ask. Alfred's running fine for me but Sonoma 14.4 seems to be breaking some stuff here and there so I'm hoping there might be at least some small updates or tweaks.

The new "Resolve Dependencies" feature is pretty neat and handy! One possible change that would be useful is on this screen:

Instead of just listing the formulae needed, it would be nice for a column called "used by" or "used in" to list the workflow that requires it (if it's used by >1 then just listing the first one would be fine)

This way we could decide if we want to download a large package or potentially just do some housekeeping and remove a workflow that might no longer be useful.

Okay thanks. I thought maybe there was a way to just dismiss the badge without unlinking it from the gallery.

macOS 14.1.1, Alfred 5.1.4 Build 2195

Some days (weeks?) ago I clicked "Check for Workflow Updates". A few workflows had actual updates, but there is one (ChatFred) which has an older version 1.5.3 on the Gallery vs. the actual latest release 1.6.1 on GitHub. So I chose to keep the newer version.

My question is: how can I clear the "Update available" badge that is obscuring the workflow's icon? :