create a new script, automatically populating the shebang line, editing the script, and making it executable.

shebang() { if i=$(which $1); then printf '#!%s\n\n' $i > $2 && vim + $2 && chmod 755 $2; else echo "'which' could not find $1, is it in your \$PATH?"; fi; }
The first argument is the interpreter for your script, the second argument is the name of the script to create.
Sample Output
$ shebang perl



By: bartonski
2011-03-09 14:47:32

What Others Think

What about #!/usr/bin/env python? For us Pythoneers.
kaedenn · 555 weeks ago
Hmm. Good question. I think that I would try to figure out if the interpreter will run inside /usr/bin/env, then fall back to $(which $1) if that didn't work. /usr/bin/env $1 --version Should return true for perl, python, ruby, bash...
bartonski · 555 weeks ago
maybe something like this... ENV=/usr/bin/env; if i=$($ENV $1 --version && echo "$ENV $1" || which $1) ...
bartonski · 555 weeks ago

What do you think?

Any thoughts on this command? Does it work on your machine? Can you do the same thing with only 14 characters?

You must be signed in to comment.

What's this? is the place to record those command-line gems that you return to again and again. That way others can gain from your CLI wisdom and you from theirs too. All commands can be commented on, discussed and voted up or down.

Share Your Commands

Stay in the loop…

Follow the Tweets.

Every new command is wrapped in a tweet and posted to Twitter. Following the stream is a great way of staying abreast of the latest commands. For the more discerning, there are Twitter accounts for commands that get a minimum of 3 and 10 votes - that way only the great commands get tweeted.


Subscribe to the feeds.

Use your favourite RSS aggregator to stay in touch with the latest commands. There are feeds mirroring the 3 Twitter streams as well as for virtually every other subset (users, tags, functions,…):

Subscribe to the feed for: