franzheidl

There's a workflow for that: http://www.alfredforum.com/topic/612-run-terminal-command-in-current-finder-directory/ It doesn't only let you CD in the current Finder directory, you can also pass the Terminal command you wish to run directly via Alfred. Just sayin'

Update: The workflow will by default execute your command in the first non-busy Terminal window it finds, otherwise open a new one. I have just added the option to explicitly run the command in a new Terminal window, just press [alt] when firing your command in Alfred 2. Either pull from https://github.com/franzheidl/alfred-workflows.git, or use the updated downlowd link: http://cl.ly/NjL6

Just fixed a bug that prevented the Workflow from running properly on the Desktop in case there's no folder open in Finder. Pull from https://github.com/franzheidl/alfred-workflows or use updated download link above. Sorry for the inconvenience, goes to show there's no thing like proper testing :/

Most certainly about a dozen people have done this already, but being too lazy to look these up I made my own Use Keyword "cdh" to cd into your currently open Finder directory. To run a Terminal Command , use "cdh [your command]". If there is no folder currently open in Finder, your command will be run in your Desktop folder. The Workflow will look for a non-busy Terminal window and use it before opening a new one. http://cl.ly/NjL6 https://github.com/franzheidl/alfred-workflows

Hi Andrew and Vero, please consider allowing individual icons for File Action workflow modules, just as much as for any other Input/Trigger type workflow modules. Use Case: I have a workflow that does EITHER A OR B as a script filter, based on whatever criteria the script filter checks for. I also want to allow for the same functionality as a file action included in the same workflow: Script Filter "Do A" or "Do B" -------------------> [Whatever Module Here] File Action "Do A" ---------------------------------> [Either another Module or use the same as Script Filter] File Action "Do B" ---------------------------------> [Either another Module or use the same as Script Filter] For the Script Filter, the feedback would contain the appropriate icon for either A or B, so it would be good to drop Icon A onto File Action "Do A" and Icon B onto File Action B accordingly.

Just built another variant of my Open-with… workflows for Textmate 2, as apparently there are still people out there using it. (While testing I found it still has some features that I miss badly in other editors or features I think the way Textmate implements them is still superior, credit where credit due!) The workflow opens your current open Finder folder or selection in Textmate 2, or can be used as a file/folder action. Alternatively you can also enter a directory or file path to open. Get it on GitHub: https://github.com/franzheidl/alfred-workflows Just download: http://cl.ly/PUFW

Just WOW.

Also on AlfPT now.

Also on AlfPT.

Just pushed my Compass Create Watch workflow to github: https://github.com/franzheidl/alfred-workflows Create and immediately watch a Compass project in your current Finder directory by keyword ("ccw") or as a file/folder action. When triggered by keyword, you can pass "nowatch" as an argument to create but not immediately watch the project. Happy styling. Download without git: http://cl.ly/MOFh

In any event you should be able to get these from Applescript. If you don't want to "waste" a Workflow Module for Applescript, you could run an Applescript as osascript in a bash script returning the paths of the selected item(s) to your shell script. Nonetheless, an option to use these as a target straightaway from Alfred would be nice.

This doesn't work yet, since Applescripts run as NSAppleScript only for now, but if you read Andrew's post above Applescript as OsaScript will return to Alfred 2. :-) I wonder whereabouts this is on the priorities list Andrew?

And if you're not comfortable with git, get them here: Open With Chocolat: http://cl.ly/PMzk Open with Sublime Text 2: http://cl.ly/PNE7

The external-Applescropt-not-running question has been answered by Andrew here. I have reworked Open With Chocolat as a workflow (as well as it's Open With Sublime Text 2 sibling) now and opensourced them here: https://github.com/franzheidl/alfred-workflows

Just opensourced two simple workflows of mine that I reworked from my v1 extension earlier if you want to have a look at how it's structured: https://github.com/franzheidl/alfred-workflows

Cool, Never tried Python for Alfred extensions/workflows, looks tempting though.

I personally don't see the need to clone a workflow directly into Alfred's Workflow directory (if you download from dropbox or cloudapp the file would end up in whatever your donwloads folder is either). I keep a seperate directory as my git repository where I export any intermediate or finished workflow or extension of my own to. Also I keep a "src" folder there for my non-binary source code as well as a resource folder, etc. For workflows from other people I keep another separate directory that holds a directory for each workflow, in case it's github hosted the individual workflow folder holds the git repo, too.

Command-C Command-C Alt-Command-C*, then Command 2 Alt-Command-C*, then Command 1 Couldn't be easier that, no? I personally prefer Alfred not to delete anything from my clipboard history. Also I like to be able to see what's in the clipboard history, as I find myself as often wanting to past the third-, fourth-, etc item in the history as often as the second one. The use case you describe seems pretty special to me, I can't see how to derive a sane general behaviour from that ranging over more than two items. --- * the configuration I use

Are you aware of Alfred's Clipboard History? You just need to enable it under Features/Clipboard/History as it's disabled by default.

David's suggestion sounds reasonable for Hotkeys and for now (in fact I quite like the idea of having one workflow for say System Commands Hotkeys, One for Application Hotkeys, etc.), but wouldn't solve my sidebar overload when it comes to extensions at all. Due to the larger item size in the Workflows sidebar (which I like per se, I'd just love to have the option to organize them ) Alfred v2 now shows 16 extensions at once in the sidebar, Alfred v1 showed more up to 23 (depending how they spread over categories), so in fact I find the matter even more pressing with v2 than with v1. Grouping items in a sidebar is a common OS X UI paradigm, and I'd still love to see it in Alfred to organize my extensions by whatever categories I want. I'd be totally happy if I had the option to create a collapsible folder or group (just like the extension categories Shellscripts, Applescripts, etc in v1 were) that can be named and drag-sorted, and then drop extensions in them.

Thanks so much Andrew, you just took a HUGE weight off my chest.

In Alfred v1, I could test for the location of an extension using Applescript (enclosing a 'do shell script "pwd"' command that returned the POSIX path of the actual location of the extension on the users disk). That required the Alfred v1 Background option to be checked to work. The use case is to locate the extension/workflow on the disk to link/include additional resources like external .scpt files to be run, custom icon files to be displayed in Applescript dialogs, etc. Now I'm trying to do the same thing with Alfred v2, but all I get is an "/" as POSIX path (which is the exact same behaviour as in v1 when the Background option was NOT checked). Here's a sample/test extension for v1 which upon keyword "twd" displays an Applescript dialog with the POSIX path to the extension: Test Extension Directory.alfredextension (Try unchecking the Background option and you'll get an "/" only instead" Here's a sample test workflow for v2 that tries to accomplish the exact same thing with Applescript but does return an "/" only either. In v2, there is nothing like a Background option for Applescript Workflow modules anymore. I suspect v2 runs an Applescript the exact way like v1 did when the Background option was unchecked (use "twd" to run): Test Workflow Directory with Applescript.alfredworkflow In v2 however using a shellscript module to do that works just fine (use "twdsh" to run): Test Workflow Directory using sh.alfredworkflow To include an extra shellscript module that only does a "pwd" to pass on to my Applescript to get the workflow path seems overkill, especially when additional queries need to be preserved. I'd be truly grateful if you could point out if that's down to the yet incomplete Applescript support in v2 (? - Everything else Applescript runs just fine in v2 so far), if there'll be some option to get the "Background" behaviour back in v2 later on, or if there is another, simpler way to test for the actual full path to the workflow directory from inside an Applescript with v2.

That's something I felt the need for with v1 already, now that what used to be Hotkeys in v1 also are Workflows, I'd appreciate an option to group Workflows in folders even more. In v1, I currently have 41 extensions installed and 18 hotkeys configured, which would sum up to 59 items in the Workflow sidebar in v2. That's quite a list to scroll. Apart from having these sorted alphabetically, I'd love to be able to put them into groups/folders, e.g. one for extensions covering aspects of my private life, one for professional tasks, a group for my own extensions, another for extensions I have under development, or even extensions that are specific to clients of mine (e.g. extension triggering client-specific build-/deployment tasks).