cands

Awesome, thank you very much for the quick and most valuable update! Now it works to search for words with Swedish characters, and it improves the usability a lot. 

Here we go v.2.2, let me know how it goes...
 
New Features
Added ability to paste tag from tag search into frontmost app
Added new flag to settings to change search behaviour to run exact match or match any string (exact_match)
Improvements
Exchanged custom html to markdown converter to pandoc. The custom converter were not able to import a some webpages. Please ensure to install pandoc (the link can be found in mdhelp or README)
rewrite of the search algorithm due to unicode issues
Bugfixes
The Search is now unicode savy, means e.g. german umlauts will now be found in md notes
Improved filename normalisation
Download via Git

With v2.0 links to multiple markdown files (File Action) can be generated into a new markdown note e.g. to collect all invoices related to an insurance
 
Download at Git

new version 0.9 is now showing available keyboard shortcuts in quicklook help

I found this answer from Alfred. 
This behavior is deliberate. Many users told us that Typinator made unwanted replacements in this situation and asked NOT to expand abbreviations in Alfred's search window. For this reason, we have made this the default behavior in Typinator 8.0.
 
However, you can revert to the previous behavior with a hidden setting.
To do so, execute the following command in Terminal:
 
defaults write com.macility.typinator2 expandInAlfred 1

Instantly create a new Alfred snippet from selected text in MacOS.
 
See 
 for the background.
 
Snippet Creator
adapted from https://github.com/derickfay/import-alfred-snippets
 
There are two keywords, both of which result in the creation of a new snippet:
 
sc - (single step) Required fields: name|keyword|content -- separated by |
sc2 (multi step) - Enter the snippet text, then you'll be prompted for the keyword / name -- in the interest of speed and simplicity the name is set to the keyword.
 
sc2 also has triggers to pre-population with selected text or clipboard contents, and is also available as a Universal Action.
 
set prefsPath in the environment variables to the path to your snippets folder - e.g. "/Users/someuser/Dropbox/Sync/Alfred 4/Alfred.alfredpreferences/snippets/"
and newSnippetFolder to your desired target folder
 
The workflow posts a notification on success to remind you of your newly created snippet.
 
https://www.dropbox.com/s/85nc52o241qobvm/snippet creator.alfredworkflow?dl=0
 
Version 0.3 (2021-08-04):
- updated to use Universal Actions
 
Version 0.2:
- updated to use a pipe | as a delimiter instead of a comma, and to remove the requirement to enclose text in quotes 
 
Version 0.1:
 initial
 
 

Thanks! I've updated the repo and the first post.

Update.
 
Added unread_order Workflow Environment Variable to control how unread bookmarks are displayed (oldest or newest first).

To update, download the latest version (same URL) or wait a few days and it’ll prompt you to on next usage, since it uses OneUpdater.
 

Word Search is an Alfred 2/3 workflow which exposes powerful word searching utilities. Ultimately, the workflow can be leveraged to widen your vocabulary and make you a better writer.
Quick Reference
syn [word] - Broadly searches for words related to a word/phrase. dsyn [word] - Searches for a word’s exact synonyms. ant [word] - Searches for a word’s antonyms. rhyme [word] - Searches a word’s rhymes. describing [word] - Searches for words that describe another word Usage
Simply type in a command. Selecting a result will copy that word to your clipboard and automatically paste it in the front most app.
Installation
Simply download the latest .alfredworkflow file and double click it to import it to Alfred. Word Search will update on its own.
Demonstration
Searching for words that describe “dog” 

 
This forum doesn't like many images. If you want to see more screenshots, checkout the github page.

Useful workflow, thank you! I wonder is it by any means possible to get battery levels of connected devices? 

sure, I'll add that ASAIC 👍

Github: https://github.com/bmunoz89/alfred-wf-bluetooth-manager
 
  
🚨 Supports Alfred 3 & 4 🚨
💻 Installation 👾
Run this command on a terminal:
brew install blueutil Now download ⏬ the last release and open it 😎. That's all!!
📸 Screenshots
    
🔑 Keywords
bset: Set the default device bc: Connect the default device bd: Disconnect the default device bcs: Select the device you would like to connect to bds: Select the device you would like to disconnect to bm: Allows to turn bluetooth on and off, and the same for updates of the workflow  
Besides that, you can add shortcuts into the preferences 👌🏽

Hi @Subject22, that's awesome, instead of going through all the hustle of setting up a fork and all, here is literally the only change we needed for this Workflow. It's only the script that needs adjusting, here is the fully working script as suggested by @cands.
@Subject22 I hope this makes it easy for you to update everything.
 
# Quit Alfred 4 and his preferences if application id "com.runningwithcrayons.Alfred" is running then tell application id "com.runningwithcrayons.Alfred" to quit end if set prefsWasOpen to false if application "Alfred Preferences" is running then set prefsWasOpen to true tell application "Alfred Preferences" to quit end if delay 1 # Wait for the processes to terminate # Restart and display processes tell application id "com.runningwithcrayons.Alfred" to activate if prefsWasOpen then tell application "Alfred Preferences" to activate end if # Display Alfred tell application id "com.runningwithcrayons.Alfred" to search  

Fixed.

Update.

Let Alfred reorder paired device order.

To update, download the latest version (same URL) or wait a few days and it’ll prompt you to on next usage, since it uses OneUpdater.
 

Thanks @cands for that tip. I changed it and updated the workflow and it works still — and hopefully will continue to do so indefinitely now.
 
@Subject22 Would you mind updating the workflow? I could even provide the ZIP if that'd help you.

Call qapps and all apps excluding the ones you set in the keep_alive Workflow Environment Variable will quit. The Finder and Alfred (including Alfred Preferences) are added to the exclusion list by default, unless you set their kill_ variables to true.



You can exclude extra apps on a per-run basis by adding them as arguments. Calling with ⌘↵ will also exclude the frontmost app.

Use the exact application names as they present themselves to the system. To prevent multiple apps from quitting, separate their names with commas.



qprocesses will kill all processes, subject to the same keep_alive and kill_ settings, meaning even things in the background that you don’t see will be asked to quit.

The External Triggers allow to temporarily override which apps to keep alive by passing them as the argument.

Note both options ask the apps to exit (SIGTERM) instead of telling them (SIGKILL). If you need to force individual processes to terminate, use ProcessControl instead.

Download | Source

The new update and release will be made on Github, not here. Pls go to the Github page if interested in this little one. It won't have frequent updates but I think it is somewhat mature now.

Please refer to the Github page for full documentation. Or download here.
 
Basically, this is a workflow that allows you to create and view your self-defined cheatsheets. "It was designed to help remind *nix system administrators of options for commands that they use frequently, but not frequently enough to remember". Alfred makes your cheat sheets searchable and enables a very quick glance at some commands with your finger tips.
 
This project was inspired by a command-line project cheat, extended its capability and yet acts as an independent tool. If you use "cheat" before, you can safely import your old cheat sheets in one hit. If you haven't heard of "cheat", you can start accumulating knowledges by writing your cheat sheets and make them searchable.
 
To list all your cheat: cheat
To search and list the content of one of your cheat: cheat <sheet name>. Fuzzy search and autocomplete is supported.
To search in a specific sheet indexed by some keyword: cheat <sheet name> <keyword>.
To search across all your sheets for some keyword: cheat --search <keyword>
 
Autocomplete and fuzzy search are supported of course.
 
For more detail and a git demo, refer to the Github page please.
 
 

This workflow sounds useful but the link is dead.

Please use extensions release page for the most recent workflow.

I've updated all of my workflows on https://github.com/raguay/MyAlfred. There are 69 workflows that I've created and use regularly (most of them). If you have any questions or problems, feel free to let me know. Since all of these were created with a need that I had, they might not all work for what you need. But, play around with them and experiment and you will learn a lot!
 
No, I will not be updating each of my individual listings in the Alfred forum or in Packal.org. That is just too large of a job for no benefit. Just get them from my GitHub account.
 
The Alfred 2 and 3 versions are still there in their own directories. Since I don't have Alfred 2 or 3 installed anymore, I will not be updating them.
 
Richard Guay

@nikivi funny you should ask - I had actually made the required changes to the framework during Alfred 4's development but didn't actually get around to implementing this in the contacts viewer. I'll add this in for the next release
 
Cheers,
Andrew

Version 8.0 is out and is now compatible with Alfred 3 and Alfred 4.

I have zsh configured with 1000's of lines of stored command history and the capability for partial history searching. That way if I begin a command I've previously used and press Up I can go through my history in reverse order of just commands with that prefix. So if I've previously typed `cd /etc/` then typed some other commands not beginning with `cd` and then later type `cd ` and key up then it jumps to the line in history beginning with `cd` which is `cd /etc/`.
 
In practice this is very useful when you know you fairly recently used a command with long params and you want to jump to it to use the same params. It's also very useful with commands that have a limited number of possible params because once you have an established history you can just type the command and scroll through all the possible params (note, history is most useful here if it is reduced to unique commands, not keying through 20 instances of using the same one or two params to find the time you used a third variation).
 
For an example use case, I'm a developer, our company has 10-20 repos/projects we're working on. There are a range of workflows and custom urls we might want to setup that might take one of these repos as a param (open GH page for the repo, open CI for the repo etc). Rather than create a separate workflow keyword or custom url for, say, 8 commands times 20 projects, 160 keywords, or laboriously typing the same repo param in full each time, this feature would allow me to just setup the 8 commands and start using them and (once I've built up the history) then I can usually complete a command by typing its name and keying up a few times. Because commands are stored in historical order keying up will also usually hit the most commonly used projects first (or you could explicitly design it to show partial history matches in order of frequency of use in the history).