zeitlings

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

Easily extract a specific page range from an existing PDF document and create a new PDF file with the selected pages. Usage Either invoke the workflow by using the keyword (default: pdfsplit) and locate a PDF, or send a PDF to the workflow's File Action. Specify the start and end pages of the range you want to be extracted. The specified first and last page can be previewed by pressing the ⌘ modifier. Specifying the Pages ↩ Proceed to extract text from the specified pages. ⌘↩ Preview the first and last PDF pages w/ Alfred's PDF View. ⌥↩ Proceed, push the result to the File Buffer and action it in Alfred. Press ↩ to return to the view where you can set the start and end pages. Dependencies With Homebrew install Poppler: brew install poppler

Extract text from PDF documents. Usage Extract the entire text from one or more PDFs by sending them to the workflow's File Action or locate a PDF with the File Filter by using the keyword (default: pdftotext). To extract the text from specific pages of a single document, use the ⌘ modifier. The result will be exported as a plain text document. File Filter ↩ Proceed to extract the entire text. ⌘↩ Proceed by specifing the pages to extract. ⌃↩ Proceed, push the result to the File Buffer and action it in Alfred. File Action ↩ Proceed to extract the entire text. ⌘↩ Proceed by specifing the pages to extract (single file only). ⌃↩ Proceed, push the result(s) to the File Buffer and action them in Alfred. Specifying the Pages ↩ Proceed to extract text from the specified pages. ⌘↩ Preview the first and last PDF pages w/ Alfred's PDF View. ⌥↩ Preview the contents of the first and last page w/ Alfred's Text View. ⌃↩ Proceed, push the result to the File Buffer and action it in Alfred. Press ↩ to return to the view where you can set the start and end pages. Dependencies With Homebrew install Poppler: brew install poppler

I played with this yesterday and the results were rather disappointing. The most limiting factor is the lack of support for markdown tables in Alfred's Text View. Syntax highlighting would also make a big difference. There were a lot of inconsistencies with pandoc, mostly around the broken tables. Html2md, a Go cli tool, produced slightly better and more consistent results, which are still messy when thrown at the Text View as it is now. Here's another alternative I found without markdown view that holds up well: alfred-devdocs.

Hey @Textdriven Unfortunately, there is no error message in the logs to suggest a solution. :cp doesn’t work because there is no color history to show yet. The only thing I can think of is this: The script is compiled on your device the first time you run the workflow. This seems to be required since macOS 14. For this to work, you may still need to install the Xcode command line tools to run the swiftc command that compiles the swift code into an executable. This can be done by running the following command in the terminal: xcode-select --install However, if I'm not mistaken, macOS should have prompted you with a popup asking you to install the command line tools if they are not present 🤷‍♂️

The subtitle reads "Type a name or email address to send an email". When you start typing, you should see options from your contacts to send an email to. If the email function (built-in action) provides the pattern, then the other functions or perhaps workflows you're trying to use will require additional input.

Depends on the IDE you are using... VS Code's CLI has the code --goto <filepath>:<line>:<character> command, for example. But how would a workflow be more convenient than hitting cmd+f, typing the word, and then cycling through the matches with cmd+g? About the arrow keys, I suggest setting up a "hyper key" and remapping hyper+h,j,k,l to the arrow keys via Karabiner or to just use ctrl+n, ctrl+p. Another option would be to check out how vim approaches the problem (incremental search), and to look for integrations with your IDE or to directly give (neo)vim a try. I don't think it's worth the effort, and I'm not even sure it's possible to devise a generic solution if you're looking to manipulate the scroll view of the app.

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!

I got curious when I saw that all models have a 200k context window and that Claude 3 Haiku beats GPT-3-Turbo in some benchmarks at half the price. I hijacked the ChatGPT workflow to use Anthropic's API instead of OpenAI's and it now works just like the original. However, it feels kind of dirty to just throw a hijacked workflow out there. @vitor: Do you plan to include Claude in the workflow? Granted, it makes little sense since the workflow is called "ChatGPT / DALL-E", but if you do, I'll be happy to share my modifications to save you some headaches.

I noticed that when stacking either the text view or the Alfred browser on top of the Alfred window, hitting Escape causes all environment variables to be lost. For my use case, I can work around the problem by looping (back into a script filter object) with an external trigger that follows the view. This recreates the stacking behavior. However, if it's not too much of a change internally, I'd like to see the environment variables preserved so that the feature can be used where the variables remain relevant.

That's what I was thinking. Additional warnings that kick in dynamically when something is off will be helpful (similar to what happens when a required variable is not set in the user-facing workflow configuration), and is probably better than silently adjusting the configuration to a setting that works. I can see this causing irritation as well.

Another problematic configuration with the same problem (that needs a different solution):

Of course, but I think I already located the problem, which is partly due to a lapse on my side: A solution could be that when "Only Stop on Markers" is checked, the amount of markers to show defaults to the count of indices in the specified closed range (Min...Max). I.e. I should have entered 10 instead of 9, but to only have 9 markers where 10 are required to cover the range makes little sense. Going from 8 to 9 in this scenario also jumps to 10 immediately (which persists) skipping 9, but going back to 8 falls back on 7 after saving.

Alfred 5.5 [2257] macOS 14.4.1 (23E224) When scaling from low to high, the slider is one number shy. https://imgur.com/a/QkfEdRE

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 @majoja I haven't been using fantastical since they've switched to the subscription model. Unfortunately, I won't be able to debug without access to the application. Looking at the code, the location should already have been matched when searching. I can't say why it is not working for you. That being said, I've been reworking the app / workflow recently, so I won't adjust the current version anymore. It shouldn't be too long before the update comes out though.

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

For flexible file extensions:

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

Hey! I just updated the workflow. The most important additions are an optional integration with OpenAI for creating literature review summaries from your documents, and a window and tab switcher for active document windows. Consider setting a hotkey for the switcher, and, of course, be aware that using GPT-4 Turbo can become expensive quickly. Download: Here is the full change log: v1.1.0 Added window and tab switcher: accessible through global option (dvn .w) or via shortcut Merge (filtered) windows and tabs into window with tabs Detach tab and open in new window (modifier: ⌘) Added optional OpenAI integration, i.e. an interface for creating literature review summaries from documents at the record action level. Save as markdown annotation file or custom metadata entry. The custom metadata entry allows for copying the summary from the record action interface. Added global option to list all tags dvn . Added global inline tag retrieval dvn #tagname Added global option to delete workspaces (dvn .) Added global option to synchronize all databases (dvn .) Added modifier to synchronize database (modifier: ⌃) Added option to back out of move, replicate, duplicate record Added placeholders for various fetch operations Added hints that an existing workspace will be updated when trying to save a workspace with an already used name Fixed unhandled case with no open database Fixed excluded databases being included in tag search Fixed attempts to save new workspaces with an empty name not being suppressed Refined overall inline tag handling

Hey @wilsonlyt Looks like it isn’t. I will add it as an option under dvn . when I get to it. While searching a specific database, e.g. via dvn |dbs|3| you can search for tags by just typing # and the first letter(s) of the tag you are looking for. Here is some more info on this. I'll try to make it available globally for the next update, too. Unfortunately no. The "brute force search" just uses Alfred's file filter which looks into the metadata of files and there is no information on groups or tags available for those afaik. Part A is just what you see first when you enter the record actions, i.e. the first 9 items. For "part B" stride down with your arrow keys, they are the items that are just not in view yet. Universal Actions are one of the features of Alfred (and something you really should familiarize yourself with to get the most out of Alfred!). It let's you act on your selection in macOS after pressing a shortcut. From the support page: Alfred uses ⌘/ by default. To act on one or more files from your DEVONthink database, try selecting these files and pressing command+shift+D. This will bring up the view for |sel|. Choosing to act on all records here is equivalent to selecting the same files, launching Alfred’s Universal-Action-Panel and activating the Action specific to the workflow; this will bring up the view for |uni|. This works from within the DEVONthink database and outside of it. If you send files to the dvn specific Action that are not already in a database, you will not see options to act on the records. Instead, you will see options that allow you to import the new files. Also, thanks for the feedback!

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).

Have you perhaps modified the workflow configuration? By default the 'open configuration' item only shows if the keyword is preceded by a colon. This is how it looks for me:

@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.

The System Profiler results don't include any information about your headphones' battery status. Without that, I'm afraid there's nothing to work off of.