Hide

What's this?

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/

Get involved!

You can sign-in using OpenID credentials, or register a traditional username and password.

OpenID
or
Sign in Register

First-time OpenID users will be automatically assigned a username which can be changed after signing in.

Hide

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:

Hide

News

2011-03-12 - Confoo 2011 presentation
Slides are available from the commandlinefu presentation at Confoo 2011: http://presentations.codeinthehole.com/confoo2011/
2011-01-04 - Moderation now required for new commands
To try and put and end to the spamming, new commands require moderation before they will appear on the site.
2010-12-27 - Apologies for not banning the trolls sooner
Have been away from the interwebs over Christmas. Will be more vigilant henceforth.
2010-09-24 - OAuth and pagination problems fixed
Apologies for the delay in getting Twitter's OAuth supported. Annoying pagination gremlin also fixed.
Hide

Tags

Hide

Functions

Hide

Credits

Site by David Winterbottom (user root).

Analyze awk fields

Terminal - Analyze awk fields
tr " " "\n" | nl
2009-08-13 14:36:18
User: dendoes
Functions: tr
1
Up
Down
Analyze awk fields

translate and number lines is simpler and you use tr to choose your delimiter (eg for csv files)

Show sample output | Add to favourites | Report as malicious

Alternatives

There are 2 alternatives - vote for the best!

Terminal - Alternatives
awk '{print NR": "$0; for(i=1;i<=NF;++i)print "\t"i": "$i}'
2009-07-23 06:25:31
User: recursiverse
Functions: awk
Tags: awk
16
Up
Down
Analyze awk fields

Breaks down and numbers each line and it's fields. This is really useful when you are going to parse something with awk but aren't sure exactly where to start.

Show sample output | Comments (3) | Add to favourites | Report as malicious

Know a better way?

If you can do better, submit your command here.

What others think

...although this only gives the right numbers for the first line of the input. Maybe then for any text file you may want:

head -n 1 filename | tr " " "\n" | nl
Comment by bwoodacre 196 weeks and 6 days ago

I always use:

fmt -1

as an easy to type alternative to:

tr " " "\n"

(it doesn't work for arbitrary delimiters, but I find it handy for splitting on whitespace)

Comment by ger 195 weeks and 5 days ago

Your point of view

You must be signed in to comment.

Related sites and podcasts