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.

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



Create a script of the last executed command

Terminal - Create a script of the last executed command
echo "!!" > foo.sh
2009-02-25 00:37:25
User: dnavarre
Functions: echo
Create a script of the last executed command

Sometimes commands are long, but useful, so it's helpful to be able to make them permanent without having to retype them. An alternative could use the history command, and a cut/sed line that works on your platform.

history -1 | cut -c 7- > foo.sh


There are 16 alternatives - vote for the best!

Terminal - Alternatives

Know a better way?

If you can do better, submit your command here.

What others think

doesn't work well with quotes in the original command

Comment by rgiar 383 weeks and 1 day ago

@rgiar: Thanks for pointing that out. I came up with a solution, the exact wording of which will vary by system:

history -1 | sed -e 's/^\ [0-9]*\ *//g' > foo.sh

You could make a function out of that, and on top of working properly, it would be simpler and more powerful than my original command.

histecho history -$1 | sed -e 's/^\ [0-9]*\ *//g'
Comment by dnavarre 383 weeks ago

You might have better luck using ctrl-x, ctrl-e and then using your editor's "save as" command.

Comment by woxidu 382 weeks and 6 days ago

ctrl-x,ctrl-e just put your present commandline to the texteditor, instead you should use "fc" command which put your last commandline to the texteditor and then you can edit and save, but the question is when you use "fc", the command will be commited after you save, anybody kowns how to save the previous commandline without running it?

Comment by byrgl5 165 weeks and 6 days ago

echo `!!`

Comment by yangfeng724 160 weeks and 1 day ago

Your point of view

You must be signed in to comment.