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.

World cup college
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

2010-03-18 - Top 10 commands explained
There's a great article by Peteris Krumins explaining the current top 10 commands: http://www.catonmat.net/blog/top-ten-one-liners-from-commandlinefu-explained/
2010-03-03 - Commandlinefu @ SXSW 2010
Am going to be at SXSW this year, in case you want to submit any CLI nuggets or suggestions to me in person. Ping me on the @codeinthehole Twitter account.
2009-09-12 - Email updates now available
You can now enable email updates to let you know each time you're command is commented on.
2009-07-11 - API and javascript blog widget now available
A simple API has been released, allowing commands to be retrieved in various formats. This also allows commands to be embedded on blogs/homepages.
Hide

Tags

Hide

Functions

Hide

Credits

Site by David Winterbottom (user root).

Empty a file

Terminal - Empty a file
> file.txt
2009-01-26 10:22:31
User: root
140
Up
Down
Empty a file

For when you want to flush all content from a file without removing it (hat-tip to Marc Kilgus).

Add to favourites | Report as malicious

Alternatives

There are 2 alternatives - vote for the best!

Terminal - Alternatives
> foobar.txt
2009-12-29 08:08:15
User: unixmonkey7657
3
Up
Down
Empty a file
Comments (1) | Add to favourites | Report as malicious
truncate -s0 file
2009-10-24 16:31:03
User: pipping
2
Up
Down
Empty a file

The downside of output redirection is that you need permissions. So something like

> file

won't play nicely w/ sudo. You'd need to do something like

bash -c '> file'

instead, you could go w/

sudo truncate -s0 file
Comments (0) | Add to favourites | Report as malicious

Know a better way?

If you can do better, submit your command here.

What others think

Nice one! Some thing in *nix are so simple that you'd never imagine they exist :)

Comment by evad 83 weeks and 3 days ago

cat > file.txt followed by shift+ins allows you to insert your buffer content into file. ^d to finish the process

Comment by boombastic 83 weeks ago

A similar useful trick which works with things like sudo and pfexec is "cp /dev/null file.txt"; that way you don't have to switch to another account to empty files which you do not own.

Comment by systemj 82 weeks ago

To avert surprises, prepend ":" to perform specified redirections reliably:

: > foo

FWIW, the (built-in) null command ":" also expands arguments.

Comment by laburu 82 weeks ago

laburu can you expand on the reliability issue you're referring to?

Comment by pixelbeat 82 weeks ago

This is especially useful with large files that need to be cleared. I've run across a situation where the inodes ran out on the hd because people kept cat'ing /dev/null and redirecting it to file. That method kept the inodes locked.

Comment by leprasmurf 81 weeks and 6 days ago

It should be noted that this is a Bash-ism. This will hang in ZSH and throw an error to STDERR with BSD-CSH.

Comment by atoponce 78 weeks and 4 days ago

Excellent! Just what I was looking for

Comment by xenon87 77 weeks and 2 days ago

If you've done set -o noclobber the command will need to be:

>| file.txt

Comment by rtmhal 76 weeks and 1 day ago

This is not just a is a Bash-ism it works fine on the korn shell too.. tested on ksh/HP-UX.

Comment by zlemini 62 weeks and 5 days ago

Perfect for clearing log files :)

Comment by okuehn 46 weeks and 6 days ago

Your point of view

You must be signed in to comment.

Related sites and podcasts