zeitlings

indeed 😄

these pdf workflows look great!

Compress PDF documents.
Usage
Either invoke the workflow by using the keyword (default: pdfcompress) and locate a PDF, or send a PDF to the workflow's "Compress PDF Document" File Action.
A compression preset can be selected by pressing ⌥ before proceeding with ↩.
File Filter

↩ Proceed to compress the PDF using the default strategy. ⌥↩ Select a compression preset. File Action

↩ Proceed to compress the PDF using the default strategy. ⌥↩ Select a compression preset. Compression Presets

↩ Proceed to compress the PDF using the selected strategy.  
The result will be a compressed document in the same location as the source PDF file.
Dependencies
With Homebrew install Ghostscript: brew install gs

Well, by setting `"type": "file:skipcheck"`, I’m able to collect URLs in the file buffer and send them to actions that accept multiple strings, which pretty much meets my needs. But the double slashes in the strings are all replaced with single ones. I suppose this wouldn’t affect file paths since there’re normally no double slashes in file paths. But if this could be fixed then the file buffer will also work for URLs (even though it wasn’t designed to do so).

@vitor
 
I think this is an important need so that export speed can be improved.
 
Thanks.

The integration is not so seamless as to not break the existing code, though. However, I forked the repo, pushed all changes and applied some cosmetics.
The code and standalone workflow are now up for grabs and can be integrated or not : https://github.com/zeitlings/alfred-anthropic
 
 
Thanks!

Usage

Search for executables in PATH via the whereis keyword.


↩ Copy original path. ⌥↩ Copy resolved path if original is a symbolic link.
⤓ Install on the Alfred Gallery | Source

Hey,
 
I am working on the next evolution of the workflow. The major changes involve the addition of an agenda, the possibility to create new events using natural language, improvements of the week view and an overall redesign. For now, the search function stays true to what it was, except that it is handled internally.
 
I'm announcing this, because I'm looking for some of you to beta test the workflow as I'm somewhat pushing the limits of what can be achieved with Alfred's plain text result items, and would appreciate knowing that it works well on different machines with different configurations. 
 
For the potential beta tester:
I am using the same tricks to right-align the icons that I use to create the tidy block calendar, and would like to know if the layout of the results (e.g. a listed calendar event) succeeds with your custom theme and configuration. One of the key challenges is to present all the relevant information clearly, given Alfred's limitations in displaying data, without making the view feel cluttered and distracting.  I'd like to get your feedback on how well this works, and your suggestions on how to possibly improve the views. Especially the agenda.  I'd also like you to test the new features and let me know if they (a) work for you as expected, (b) are intuitive for you or not, (c) are buggy in any way or broken due to your locale. Permissions authentication has changed recently, and I am wondering if you are having problems granting access to your calendars, and if so, how you may have resolved them. Note that the workflow requires Apple's SF Symbols to be installed for the icons to show.
Please let me know if you're interested!
 
 
Here are some previews:
 



(Creating an event, you can adjust the day using > and <, as well as the time using + and -)

Hey,
 
I am working on the next evolution of the workflow. The major changes involve the addition of an agenda, the possibility to create new events using natural language, improvements of the week view and an overall redesign. For now, the search function stays true to what it was, except that it is handled internally.
 
I'm announcing this, because I'm looking for some of you to beta test the workflow as I'm somewhat pushing the limits of what can be achieved with Alfred's plain text result items, and would appreciate knowing that it works well on different machines with different configurations. 
 
For the potential beta tester:
I am using the same tricks to right-align the icons that I use to create the tidy block calendar, and would like to know if the layout of the results (e.g. a listed calendar event) succeeds with your custom theme and configuration. One of the key challenges is to present all the relevant information clearly, given Alfred's limitations in displaying data, without making the view feel cluttered and distracting.  I'd like to get your feedback on how well this works, and your suggestions on how to possibly improve the views. Especially the agenda.  I'd also like you to test the new features and let me know if they (a) work for you as expected, (b) are intuitive for you or not, (c) are buggy in any way or broken due to your locale. Permissions authentication has changed recently, and I am wondering if you are having problems granting access to your calendars, and if so, how you may have resolved them. Note that the workflow requires Apple's SF Symbols to be installed for the icons to show.
Please let me know if you're interested!
 
 
Here are some previews:
 



(Creating an event, you can adjust the day using > and <, as well as the time using + and -)

The script filter expects a specific JSON object as a result that contains information about what to display. Instead of echoing the argument directly, you have to wrap it in this format if you want it to "see" what you typed. Otherwise Alfred will jump to the default fallback because it doesn't know what to do. There is a script filter example under the "getting started" section when creating a new workflow that lets you inspect the format.
 
In short, you would want to do something like this:
 
local input="placeholder" [[ ! -z "$1" ]] && input="$1" cat << EOB {"items": [ { "title": "$input", "subtitle": "$input", "arg": "$input" } ]} EOB  

<Drowning noises off>
 
I, too, moved from TextExpander the moment it went subscription. But, really, I'd be hard put to abandon Typinator: I have so much in it, including "mini-programs" that Do Things™️.
 
While my brain is certainly small enough to fit in a Snippet 😁 I have reason to suppose you might be well qualified to prepare some sort of presentation on Snippets. 😉
 
Stephen

v1.2.0 implements the new grid view for the color history
 

v1.2.0 implements the new grid view for the color history
 

Pick a color to get its hex, rgba, hsl representation or NSColor initializer.
 

Usage
Activate the Color Sampler with the keyword (default: cp) and pick the desired color.

Color History
To review previously picked colors, activate the workflow with the keyword preceded by a colon (default: :cp).

Pick a color to get its hex, rgba, hsl representation or NSColor initializer.
 

Usage
Activate the Color Sampler with the keyword (default: cp) and pick the desired color.

Color History
To review previously picked colors, activate the workflow with the keyword preceded by a colon (default: :cp).

LaTeX ⟷ Markdown Alfred Workflow
Quickly convert Markdown to LaTeX or vice versa from your clipboard with Pandoc.

Description
A simple routine to convert snippets of markdown to LateX from your clipboard or vice versa. The workflow creates either a *.md or *.tex file relative to your input and at the location you choose. The file is converted with Pandoc by calling it from the terminal. The converted file subsequently gets output at the same place. Existing files will be overwritten.
 
Pandoc is key and has to be installed:
$ brew install pandoc GitHub: 
github.com/zeitlings/alfred-latex-md/raw/master/LaTeX-MD.alfredworkflow (direct download) 
github.com/zeitlings/alfred-latex-md
  Alternative Method: Clipboard only
An altered version that removes all created files and copies the converted output back to your clipboard:
 
Convert markdown to LateX from your clipboard or vice versa. The workflow creates either a  *.md or *.tex file at your ~/Documents folder. The file will be converted with pandoc by calling it from the Terminal. The contents of the converted file will be copied to your clipboard. Both files will be moved to your trash bin.
 
 
 
GitHub: 
github.com/zeitlings/alfred-latex-md-direct/raw/master/LaTeX-MD-direct.alfredworkflow (direct download) 
github.com/zeitlings/alfred-latex-md-direct
 
_____________
 
The workflow is piggybagging off these two:
https://www.alfredforum.com/topic/459-workflow-create-a-new-text-file-with-clipboard-content/
https://www.alfredforum.com/topic/394-fixed-create-a-new-file-in-the-finder/
 
https://pandoc.org/
 
 
 

Hey, two suggestions for the configuration builder:
Drag-and-Drop to reorder the fields (please) Add option-sets as a new base type   
What I have in mind is very similar to "Popup Selection". You can define a set of items, but instead of allowing only one of the options to be selected, all options can be added as needed. What can be added is predefined, which prevents the user from passing incorrect values to the workflow. Take, for example, the language options in the OCR workflow. Instead of copying and pasting "es-ES, pt-BR, zh-Hans", the NSTokenField would autocomplete to the appropriate option (based on the item label).
 

 

Added to version 1.2.0

 
OCR Light v1.2.0
Add File Action to extract text from images Fix for macOS Sonoma (Compiles the script en passant to compensate for the failure to link objc symbols on macOS 14).

Ah, I must have done that unknowingly. This is fixed. Thank you so much for this great workflow! I really like that I could increase the font size of the Preview window. That really helps this pair of old eyes!
 

@Belfong try to make it a habit to press Shift ⇧ to preview, as this will work for anything that can be previewed. Pressing return will always either pass an argument or cause an autocomplete. It is possible to show a quicklook preview this way, but it will open in a new window that has to be closed manually. At this point you can just open the dictionary application, which I think defeats the purpose.

Pick a color to get its hex, rgba, hsl representation or NSColor initializer.
 

Usage
Activate the Color Sampler with the keyword (default: cp) and pick the desired color.

Color History
To review previously picked colors, activate the workflow with the keyword preceded by a colon (default: :cp).

THANK youi!

Search for a Homebrew package via the `bi` keyword. ⏎: Install the package (`brew install`) in the Terminal. (Uses the terminal app you have configured in your Alfred settings.) ⌘⏎: Open the package's homepage (`brew home`). ⌥⏎: Copy the package's homepage to the clipboard. ⇧⏎: Show package information (`brew info`) in Large Text. Reinstall a package already installed on your system via the `br` keyword (`brew reinstall`). Uninstall a package via the `bu` keyword (`brew uninstall`). Optionally, use the `--zap` option for a clean uninstallation. Search and install fonts available in the Homebrew font tap via the `bf` keyword (`brew install font-…`).  
➡️ https://github.com/chrisgrieser/alfred-homebrew
 

@zeitlings I finally got it. Yes, I see your technique - very clever! Thanks for the tip.

Hey @TomBenz, that sounds like a job for a different workflow and somewhat niche.
If you want to adapt the workflow to do that, I'd start with passing (a) the text file location $loc and (b) the keywords, i.e. the query as $1 for zsh argv to a “Run Script” object that runs your python script.
 
The script should look something like this (not at all tested):
 
import os.path import sys from docx import Document from docx.enum.text import WD_COLOR_INDEX from nltk.tokenize import sent_tokenize filename = sys.argv[1] keywords = sys.argv[2] search_words = keywords.splitlines() matches = [] sentences = sent_tokenize(text) for word in search_words: for sentence in sentences: if word in sentence: matches.append(sentence) doc = Document(filename) for para in doc.paragraphs: for items in matches: start = para.text.find(items) if start > -1: pre = para.text[:start] post= para.text[start+len(items):] para.text = pre para.add_run(items) para.runs[1].font.highlight_color = WD_COLOR_INDEX.YELLOW para.add_run(post) # Save the output in new doc file at selected file location root, extension = os.path.splitext(filename) output_filename = root + "_KeySent_Highlights_C1" + extension doc.save(output_filename) sys.stdout.write(output_filename) # e.g. to reveal the file with Alfred