Andrew

@user01 the searches you are referring to are the default fallback searches. You can leave all the web searches enabled (as these will only show when you use their keywords).
 
To change the default fallback searches, use the "Setup fallback results" button under the Features > Default Results tab.
 
If you set duckduckgo as your top default result, then you can type bang searches directly into Alfred
 
Cheers,
Andrew

I'll take a look at tweaking this wording in the next update for clarity.

I intend to add hotkey configuration to the config builder / workflow configuration. There is some additional complexity to this compared to other text based fields as you can't define a variable in the hotkey field.
 
Cheers,
Andrew

If you update to Alfred 5.1 b2130, this should now work as expected
 
Thanks for your help and patience with this.

Looks like you were right. I was using a VPN and that must have caused a routing issue.
Once I disconnected from it, the download link worked.
 
Thanks!

I'll take a look at improving this on the import.
 
This is a good indication that we need better documentation on how to use the UI config too, as in this example, the checkbox text is not following best practices. In this case, the checkbox text should really be "Always save the conversation to file", as that is how a screen reader (VoiceOver) would see the option.
 
In this case, it would be best to have the label on the left as "Persistence" or "History", the checkbox as "Always save the conversation to file", then the first paragraph of the subtext as "Useful for not forgetting ChatFred's reply". Also, by keeping the labels / groupings as succinct, it will leave more space for the content of the preferences.

I'll take a look at improving this on the import.
 
This is a good indication that we need better documentation on how to use the UI config too, as in this example, the checkbox text is not following best practices. In this case, the checkbox text should really be "Always save the conversation to file", as that is how a screen reader (VoiceOver) would see the option.
 
In this case, it would be best to have the label on the left as "Persistence" or "History", the checkbox as "Always save the conversation to file", then the first paragraph of the subtext as "Useful for not forgetting ChatFred's reply". Also, by keeping the labels / groupings as succinct, it will leave more space for the content of the preferences.

This is now possible in Alfred 3.1 by wiring the output of the Large Type to a Delay utility for 2 seconds, then to a Hide Alfred utility.
 
Cheers,
Andrew

@donci27 You need to enable snippet expansion before this checkbox is visible. On the main Snippet prefs, tick the box in the top right "Automatically expand snippets by keyword"

@saor47 This should now be fixed in the 5.1 b2129 pre-release

@CJK Alfred doesn't process the output of a Run Script object in any way, and osascript non-optionally appends a newline to any output (which could be seen as an osascript bug, but I suspect this behaviour will never change).
 
You have a couple of options:
 
1. If you switched your script to bash, then use echo -n for output, you'll get the output as expected.
 
2. Add a Transform utility object after your Run Script set to trim the output. This will remove the newline from your osascript.
 
This has come up before, and my opinion remains that Alfred shouldn't automatically process the output of ant Run Script objects (e.g. to trim), as this would lead to more unexpected behaviour than not.
 
Cheers,
Andrew
 
[moving to workflow help].

@ivm There is mixed encoding which is what is causing the issue. For this specific case, if you switch from using a Custom Search to using a Workflow, then you get more control over the encoding.
 
Create a workflow with a Keyword wired into an Open URL:
 

 
Configure the Open URL with your specified URL, then uncheck the option to Encode {query} placeholder:

I've just tested this and it works as expected  

I'll take a look at improving this on the import.
 
This is a good indication that we need better documentation on how to use the UI config too, as in this example, the checkbox text is not following best practices. In this case, the checkbox text should really be "Always save the conversation to file", as that is how a screen reader (VoiceOver) would see the option.
 
In this case, it would be best to have the label on the left as "Persistence" or "History", the checkbox as "Always save the conversation to file", then the first paragraph of the subtext as "Useful for not forgetting ChatFred's reply". Also, by keeping the labels / groupings as succinct, it will leave more space for the content of the preferences.

Thanks for fixing! Looks like it works fine on 5.1.2133 🙂

@octothorpe if you manually use the macOS lock combo of control+command+Q does this lock your Mac?
 
If so, try quitting Alfred, then removing him from the macOS Security & Privacy > Privacy > Accessibility preferences, and re-adding him back again. If there is an underlying mismatch in the macOS privacy prefs, Alfred may have been blocked from simulating a lock.
 
If this combo doesn't work, then you can check what combo is expected under the Apple logo in the top right of your screen for "Lock Screen". This is the combo you'll need to manually configure in a workflow.
 
Cheers,
Andrew

Think of Environment Variables as workflow developer global variables / constants which will be seen throughout the workflow, and set on the scripting environment. If you're never intending to share your workflow, it'll probably be faster to just put variables and values in here.
 
User Configuration (Renamed Configuration Builder in v5.1) is designed to make it easier for users when you share your workflow. Any items needed to configure or tweak the configuration of your workflow can be presented to the user in a simple and consistent UI. This UI is also presented to the user when they install or update the workflow.
 
Under the hood, they are used in the same way.

@luckman212 good good
 
If you update to 5.1 b2132, I've actually tweaked the URL scheme to be alfredpreferences://navigateto/... but it'll be backwards compatible with the link you're using (for now). If this URL scheme is ever officially supported, it'll certainly use navigateto/

Alfred doesn't sort Universal Actions by default to keep the order predictable. You can enable the actions to be sorted by last used per type in Prefs > Features > Universal Actions > Action Ordering.

Alfred doesn't sort Universal Actions by default to keep the order predictable. You can enable the actions to be sorted by last used per type in Prefs > Features > Universal Actions > Action Ordering.

If you update to Alfred 5.1 b2130, this should now work as expected
 
Thanks for your help and patience with this.

I'll actually be adding the ability to sort workflows by Gallery Updates in the next release  

@xilopaint this is now fixed in the 5.1 b2129 pre-release

Thanks for your patience on this issue, the 5.1 b2129 pre-release now has the authorised provisioning from Apple to show you notes again.

I really appreciate the amount of work that has gone into the 5.1 pre-release: there are some very significant improvements and, although I don't believe it's specifically mentioned, I think, under Ventura, I may have been able to revert to Alfred default search scope setttings—which means that I no longer receive cluttered search results as a result of having had to set the default to \.
 
Many thanks to @Andrew (and to @vitor for what I suspect may have been supporting work on Gallery related issues).
 
Easter joy all round here..!
 
Stephen

@giovanni the 5.1 b2129 pre-release no longer lower-cases the keyword field, so you should be able to use case sensitive variable names now