Search the Community
Showing results for tags 'zsh'.
Found 4 results
I often cut/copy a bunch of text, then switch to BBEdit, then create a new document, then paste the text. I realized today that this is stupid and inefficient, when all I really need to do it pbpaste | bbedit so I created an Alfred workflow that does just that. http://share.luo.ma/alfred/bbpaste.alfredworkflow Note: To use this you'll need BBEdit installed, obviously, but also the bbedit command line tool. If you purchased BBEdit from the Mac App Store, you will have to download and install them from here: http://www.barebones.com/support/bbedit/cmd-line-tools.html
Hi, I just installed ohmyzsh (https://github.com/robbyrussell/oh-my-zsh A collection of themes and plugins to supercharge zsh. Basically, these are jst .zsh and .md files) and wanted to browse through its files and folders. All these these and plugins are installed in a folder located at ~/.oh-my-zsh I created a workflow with a file filter action but couldn't make it work. I guess it is because its files and folders are located in one hidden folder. The workflow works when the folder is renamed ~/oh-my-zsh.
Hi Everyone, I have a created a workflow for quickly loading iTerm with 4 preset tabs: 1. rails server (will start automatically) 2. rails console (will start automatically) 3. prompt (an empty tab for all your bash needs) 4. rspec guard (will not start automatically) By launching Alfred and typing 'rails' you will launch these 4 tabs. Afterwards, you can easily switch to these tabs from anywhere by launching Alfred and typing: 1. rs 2. rc 3. prompt 4. guard I made a blog post about this here: http://eyaleizenberg.blogspot.com/2014/07/3-alfred-workflows-to-make-your-rails.html Let me know what you think, Thanks.
It would be awesome to be given the option to input an arbitrary path to a binary in the "Language" specifier for the various workflow components. This would allow for supporting alternate shells (I've seen a few zsh suggestions on here) or language runtimes (like node). While this could cut down on workflow portability, it would be the workflow author's job to identify requirements to people for the workflow to function. Another reason for arbitrary paths would be to easily support updated/alternate versions of existing language binaries. For example, the built-in OS X version of Ruby is currently versioned 1.8.7-p358. Ruby version 1.8.7 will be officially deprecated as of this summer. Again, workflow authors could provide instructions on installing and using up-to-date interpreters.