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.

UpGuard checks and validates configurations for every major OS, network device, and cloud provider.

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



Copy history from one terminal to another

Terminal - Copy history from one terminal to another
history -w <switch to another terminal> history -r
2009-02-17 17:11:31
User: tlknv
Copy history from one terminal to another

Or just do history -w before opening another terminal.


There is 1 alternative - vote for the best!

Terminal - Alternatives

Know a better way?

If you can do better, submit your command here.

What others think

This works if the two terminal are using the same history files.

use "echo $HISTFILE" on each terminal to check. If they are the same or both empty, that's fine. Otherwise change the $HISTFILE on the second terminal so that it is the same as the first terminal's $HISFILE by doing "export HISTFILE=/path to/histfile" before doing "history -r".

history -w writes the shell history to $HISTFILE

history -r retrieves the its shell history from $HISTFILE.

Hence they must be the same $HISTFILE.

Comment by harryhaller 457 weeks and 2 days ago

better way in .bashrc :


shopt -s histappend

# setting the histappendoption, which will mean

# that when you close a session, your history will be appendedto the .bash_history

PROMPT_COMMAND="history -n; history -a"


Comment by wolvverine 200 weeks and 5 days ago

Your point of view

You must be signed in to comment.