davedelong

+1 for this request. Since Alfred is always running on my computer, I rarely _quit_ it. I would love it if it could keep itself updated, so I don't have to deal with clicking through screens to do it myself.

Modifiers are the reverse of what I want to do. A modifier would let me have a single keyword action go to multiple outputs. I want multiple keywords going to a single output.

I have a workflow with two nearly identical keyword triggers and two nearly identical terminal commands. The terminal commands differ only in one regard: which user I want to perform the command as (root vs the current user), and the triggers differ only in the prompt text. It looks like this: ┌─────┐ ┌─────┐ │ dev │ → │ cmd │ └─────┘ └─────┘ ┌─────┐ ┌─────┐ │ dev │ → │ cmd │ └─────┘ └─────┘ Ideally, I'd like to have a way to pass an extra parameter into the terminal command, so that I can make it more like this: ┌─────┐ │ dev │ └─────┘ ↘︎ ┌─────┐ │ cmd │ ┌─────┐ ↗︎ └─────┘ │ dev │ └─────┘ The Terminal command is rather complex, and if I have to update it, I'd like to only update it in one spot. Is there a way I can pass additional information in to the command based on which trigger is invoking it?

I'm interested in making a custom workflow that behaves like the following scenario: the user types the keyword "disk" into Alfred the results shows a list of all of the volumes associated with the computer the user selects one of the volumes (ex: "Macintosh HD") and presses "enter" the search field updates to read "disk Macintosh HD" the results update to show a list of options that can be performed on the disk, like "Open in Finder", "Open in Terminal", "Get Info", etc the user selects one of these options and presses "enter" to perform the action I've been poking around in Alfred, and I know how to do steps 1-3 and 5-6. What I don't know is how to tie them together. How can I make it so that selecting one alternative updates the UI to present more alternatives?

I ended up doing something similar (logging to a file), and that helped me realize I was trying to fetch way too much information and was blocking execution.

A "Copy to Clipboard" output does nothing for me. Is there any other way of debugging workflow scripts that work great in terminal, but not at all in Alfred?

Request: add a "url" attribute. Alfred could then interpret that URL as saying "when this item is selected in the list, open this url". This would be great for any sort of "search" workflow (google, wikipedia, documentation, etc).