echo -n '#!'$(which awk)

before writing a new script

Try it this way...

-2
By: SuperFly
2012-02-13 12:15:41

3 Alternatives + Submit Alt

What Others Think

echo '#!/usr/bin/env bash'
tusooa · 327 weeks ago
still a bad idea.. so many useless typing. in the worst case, open you file in vi type !!which awk and then i#! in worst case...
makidoko · 326 weeks and 6 days ago
Tusooa has the right idea. With /usr/bin/env, you get whichever version of the interpreter your environment is using, without having to think about where it is.
Fudo · 326 weeks and 6 days ago
How about using vim-bashsupport? See http://www.vim.org/scripts/script.php?script_id=365 This will automagically insert the proper lines depending on filetype. And some useful comment, and...
joedhon · 326 weeks and 5 days 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?

commandlinefu.com 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.

» http://twitter.com/commandlinefu
» http://twitter.com/commandlinefu3
» http://twitter.com/commandlinefu10

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: