nikivi

Say I find a snippet
 

 
I want to be able to quickly delete it right from this search. `cmd+shift+delete` or `cmd+delete`. 

Right now to delete. I have to first open it with `cmd+return`. Then I can't even delete it here:
 

 
I have to cancel. Then after cancel the snippet is not focused, so I can't immediately press cmd+delete either:
 

 
Thus can't even automate it without some image recognition.

Please add a fast way to delete snippets from the search. It's essential feature for me if I was to use Alfred Snippets heavily for all my snippets as I cycle some snippets and need that fast ability to delete them.

Thank you lots. ♥️

You mean snippets.alfdb.

That will work (it’s a SQLite database), but you may have an easier time looking inside the Alfred.alfredpreferences bundle. Can’t miss it once you do, and the organisation is straightforward.

Do keep in mind that if you plan on editing from the external interface, that may work but (naturally) isn’t officially supported and there’s no guarantee the format won’t change (after all, it is internal and not user-facing).

Usage

Convert HEIC images to JPEG via the Universal Action.



Alternatively, find images with the heicjpeg keyword.



JPEGs are saved to the Save Folder set in the Workflow’s Configuration but you can imediatelly move them to another destination by choosing Move to New Location in the After Conversion configuration. Other options include showing a notification, revealing files in the Finder, and appending to the File Buffer.

The workflow will avoid overwriting any existing files, opting to stop rather than replace data.

⤓ Install on the Alfred Gallery | Source
 

That’s the export panel, Nikita. You have click the [x] in the editor and go to the last tab.

Perhaps I should move this topic into 'feature requests' section. I rely on this action a lot in my workflow but I really don't have any idea as to how I can find a solution to this.
 
Another option is to look into building a file filter of my own but my request seems like such a trivial thing to add and Alfred's file filter is staggeringly fast. I doubt my implementation would be as fast.

A quick Google suggests it could be the Font Awesome Workflow?

Oh gosh! Honestly. You guys have really really outdone yourselves with Alfred Gallery. This thing utterly rocks. The integration with the workflow GUI is just stellar. Old workflows that are available show an upgrade, existing ones that are up-to-date with that cool little comet icon. One place to check for update. Resolve dependencies. 😍
 
I am just ever so slightly missing some filtered lists on the web page like "New" / "Updated" / "Popular, but I expect they will come with time. 
 
A huge, stellar enthusiastic thumbs up 👍

Yep, this is the intention. You can currently share themes to our main site, but I wanted to create a new system instead of migrating over the legacy system. I can't give timescales on when this will happen though.

Works great with VSCode GitHub Dim theme (https://marketplace.visualstudio.com/items?itemName=GitHub.github-vscode-theme) & iTerm theme (https://github.com/cdalvaro/github-vscode-theme-iterm).
 
Download: https://www.alfredapp.com/extras/theme/jzs9j2Kqmu/

I actually already have an internal ticket for password fields. This wasn't added in v5 due to wanting to also encrypt the value (or place it in the keychain), which adds a whole extra amount of complexity.
 
I like the idea to add a "masked" option to the text field, I'll add another ticket for this.

I agree, it would be nice if this was baked in. I wonder if Alfred can integrate OneUpdater into Alfred itself.
 
As an example, if workflow author includes a link that leads to GitHub repo and checks in `Update check` checkbox:
 

 
It would do a similar thing to OneUpdate, check the new releases as anything inside the workflow gets called and prompt for an update. No need to carry around a OneUpdater block and connect it to everything inside the workflow.
 
Would be nice.  

Without intending to sound sycophantic, I just wanted to thank Andrew (and Vero) for, not only the development and release of Alfred 5 (which is a significant, and much appreciated, step forward), but the constant, considerate and always responsive support provided on these forums.
 
It's because of the continuing development and the support here that I am intensely loyal to Alfred.
 
Thank you.
 
Stephen

Alfred Gallery is exciting news for non-coders, but a vscode extension for Alfred would mean an incomparable boost for developers imho.
 
Vscode and Alfred are my top 2 favorite macOS softwares. Integrating both experiences would be amazing news.
 
Please @vitor, come to the rescue! 😄

I love Alfred but the worst part of it is debugging. I would love to have a vscode extension which outputs in the console's editor the same content as Alfred Debugger. It would make the development experience much less annoying as we can focus in a single app (vscode).
 
@Vero @Andrew

It is. Use find . -name 'projects'.
 
 
Search in Alfred for ?keyword g and you should see the possible culprits.
 
Another way is to backup your Alfred Preferences, then go into your Workflows directory and delete them in batches of (say) 10 and try again until it doesn’t break. Then you narrow it down from the last batch.
 
 
The prompt is from macOS, not Alfred. Alfred doesn’t know that will happen before trying to run it, and trying to find out on every run could have a noticeable lag (checking for code signature is slow).
 
 
That would again have tradeoffs for all for an extremely niche and rare need. See if Console.app registered the occurrence. It may have the full path to the binary.

This may warrant creating a separate thread to this one, but if you let us know what features you're looking for, we may be able to help you achieve it with Workflows and a Snippet Trigger. There's so much flexibility in using Snippet Triggers, there's a good likelihood what you're looking for is already possible

When I show a contact's details, I would like to see their current age, i.e., how old the person is at present based on their birthdate.

Once Alfred 5 is out and settled, the Alfred Workflow Gallery will be our top priority, including integration directly into Alfred.
 
The Workflow foundation changes I've made in Alfred 5 pave the way for some really exiting new features (for Alfred 5.1, 5.2 etc). We'll be sharing details in due course!
 
Cheers,
Andrew  

Would really like to see the workflow gallery a top priority and included as an actual in-app package manager. While the announced changes sound like improvements, they seem to be missing the features (would love customizable detailed result panes in addition to the package manager) that really benefit the user experience in Alfred alternatives.

We've just published the first sneak peek of Alfred 5's features!
 
Creating workflows will be faster, more user-friendly and accessible than ever with Alfred's new Palette, Prefabs, Automation Tasks and a totally revamped Workflow Editor. 
 
Early Access begins later this month. We can't wait to share this new release with you!  
 
https://www.alfredapp.com/alfred-5-whats-new/
 
Feast your eyes on the new Workflow Editor with all the goodness that will make creating workflows even more efficient!
 

We're planning an Alfred workflow gallery, to which creators will be able to contribute their own workflows.  
 
The project has been in the works for some time but, as a small team, we've prioritised getting a fantastic Alfred 5 release out first.  Once Alfred 5 has launched and users are happily up and running with the new features, we'll be working on an official site for Alfred workflows, as a separate project to v5.
 
Our aim is to create a safe and organised platform, which is easily searchable and browsable.

I currently either use AwGo update system or OneUpdater.

There is a post on Reddit of it too. I agree with top comment about having some kind of easier way to find and perhaps even publish workflows.

Just saw the blog post and I’m wicked curious to know what this will bring!

When configuring a Run Script or Script Filter, Alfred provides a Language dropdown listing the runtimes which have historically been included with macOS. But what if you want to run a script from another language which you have installed on your system? Be it Node.js, Lua, or something else, it’s dead-simple to call them. Either:
Save your script with a proper shebang (examples: #!/usr/bin/env node; #!/usr/bin/env lua) and use External Script as the Language, pointing to your script. Use /bin/zsh (or /bin/bash) as the Language and tell the runtime to call your script (examples: node MY_SCRIPT.js; lua MY_SCRIPT.lua). The first executes (marginally) faster but the second allows you to send preset arguments to your script. They work as they are assuming the languages were installed with Homebrew, as Alfred includes its directories in its PATH.