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.

Get involved!

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.

Universal configuration monitoring and system of record for IT.

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:



May 19, 2015 - A Look At The New Commandlinefu
I've put together a short writeup on what kind of newness you can expect from the next iteration of clfu. Check it out here.
March 2, 2015 - New Management
I'm Jon, I'll be maintaining and improving clfu. Thanks to David for building such a great resource!

Top Tags



Psst. Open beta.

Wow, didn't really expect you to read this far down. The latest iteration of the site is in open beta. It's a gentle open beta-- not in prime-time just yet. It's being hosted over at UpGuard (link) and you are more than welcome to give it a shot. Couple things:

  • » The open beta is running a copy of the database that will not carry over to the final version. Don't post anything you don't mind losing.
  • » If you wish to use your user account, you will probably need to reset your password.
Your feedback is appreciated via the form on the beta page. Thanks! -Jon & CLFU Team

In place line numbering

Terminal - In place line numbering
{ rm -f file10 && nl > file10; } < file10
2010-04-08 21:08:23
User: zlemini
Functions: nl rm
In place line numbering

Add permanent line numbers to a file without creating a temp file.

The rm command deletes file10 while the nl command works on the open file descriptor of file10 which it outputs into a new file again named file10.

The new file10 will now be numbered in the same directory with the same file name and content as before, but it will in fact be a new file, using (ls -i) to show its inode number will prove this.


There are 2 alternatives - vote for the best!

Terminal - Alternatives

Know a better way?

If you can do better, submit your command here.

What others think

It should be noted that this can be dangerous. If the command fails for some reason (disk full, syntax error, Ctrl-C pressed, whatever), you'll have an empty file and no backup.

I think it's always better to use a temporary file:

nl file10 > file10.new && mv -f file10.new file10
Comment by inof 358 weeks and 4 days ago

Your comments about syntax, disk full etc are not specific to this command, they apply to most of the commands on this site.

Be advised, the 'rm' command above deletes the directory entry which is only a reference to the actual inode.

Be more specific as to why you think it is dangerous and i will glady look into improving it.

Comment by zlemini 358 weeks and 4 days ago

I agree with inof. Both versions use two inodes and just manipulate dentries to get the naming right, so neither is more efficient. But inof's version obviously can be interrupted, and the mv doesn't happen until nl has finished. Whereas with rm && nl you may interrupt, and have rm complete without nl finishing, and you are left without a file. It is true that a similar criticism applies to many of the commands at this site, but in this case by rearranging the operations, I think the "danger" is lessened. I think relying on the dentry/inode behavior of the filesystem layer is neat, but inof's version is more OS-agnostic. Would this work under Cygwin?

Comment by bwoodacre 358 weeks and 4 days ago

The issues with replacement using this method are documented at:


Comment by pixelbeat 358 weeks and 1 day ago

Your point of view

You must be signed in to comment.