commandlinefu.com is the place to record those command-line gems that you return to again and again.
Delete that bloated snippets file you've been using and share your personal repository with the world. 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.
If you have a new feature suggestion or find a bug, please get in touch via http://commandlinefu.uservoice.com/
You can sign-in using OpenID credentials, or register a traditional username and password.
First-time OpenID users will be automatically assigned a username which can be changed after signing in.
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
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:
There is 1 alternative - vote for the best!
( IFS=:; for i in $PATH; do echo $i; done; )
echo $PATH|sed -e 's/:/\n/g' # but the tr one is even better of course
echo $PATH|xargs -d: -i echo {} # but this comes up with an extra blank line; can't figure out why and don't have the time :(
echo $PATH|cut -d: --output-delimiter='
' -f1-99 # note -- you have to hit ENTER after the first QUOTE, then type the second one. Sneaky, huh?
echo $PATH | perl -l -0x3a -pe 1 # same darn extra new line; again no time to investigate
echo $PATH|perl -pe 's/:/\n/g' # too obvious; clearly I'm running out of ideas :-)
If you can do better, submit your command here.
You must be signed in to comment.
'tr' is more right command
echo $PATH | tr ':' '\n'