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



Changing the terminal title to the last shell command

Terminal - Changing the terminal title to the last shell command
trap 'echo -e "\e]0;$BASH_COMMAND\007"' DEBUG
2009-09-29 21:09:21
User: Vereb
Functions: trap
Changing the terminal title to the last shell command

You can set the previous bash command as the terminal title by this command.


-trap assigns a command to execute at a given bash signal.

-in the $BASH_COMMAND you find the last command

-you can set the terminal title with the escape sequence: \e]0;this is the title\007

-to let the echo care about the backslashes give the -e to it

Since trap is a built in bash command you find more informatin in 'man bash'for more

Source: http://www.davidpashley.com/articles/xterm-titles-with-bash.html


There is 1 alternative - vote for the best!

Terminal - Alternatives
if [ "$SHELL" = '/bin/zsh' ]; then case $TERM in rxvt|*term|linux) preexec () { print -Pn "\e]0;$1\a" };; esac; fi
[[ "x$TERM" == "xrxvt" || "x$XTERM_VERSION" == xXTerm* || "x$COLORTERM" == 'gnome-terminal' && "x$SHELL" == */bin/zsh ]] && preexec () { print -Pn "\e]0;$1\a" }
2009-10-05 15:39:45
User: Patola

Found another way, more compatible. Tested with xterm, aterm, gnome-terminal and rxvt (where it sets the window title) and guake (where it doesn't - after all, guake does not show the window title).

Know a better way?

If you can do better, submit your command here.

What others think

Holy crap, that's nice!

I've got plenty of aliases that wrap lengthy commands and give me feedback in the titlebar. Your trap combined with a PROMPT_COMMAND opens up a whole new world!


Comment by flatcap 356 weeks and 4 days ago

Doesn't seems to work when sending process in background using "&"

Comment by eastwind 356 weeks and 3 days ago

I don't have a problem with background tasks -- they show up as expected. However, I do see an unnecessary newline after every command. Try changing the command to use:

echo -ne
Comment by flatcap 356 weeks and 3 days ago

Just for fairness, I found the similar trick in zsh:


Although for the behaviour to be really identical, I'd change the code from the above URL to:

# Last command on window title:

if [ "$SHELL" = '/bin/zsh' ]


case $TERM in


preexec () { print -Pn "\e]0;$1\a" }




Comment by Patola 355 weeks and 5 days ago

Yes, you are right, i found it there. I didn't want to be unfair.

I started to collect these useful scripts here. I should have mention the source, sorry!

Comment by Vereb 355 weeks and 4 days ago

What about bash ENV.?

does any remedy there?

Comment by krax 240 weeks and 1 day ago

Your point of view

You must be signed in to comment.