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





Make changes in .bashrc immediately available

Terminal - Make changes in .bashrc immediately available
. ~/.bashrc
2012-10-13 09:07:02
User: xamaco
Make changes in .bashrc immediately available


There is 1 alternative - vote for the best!

Terminal - Alternatives
source ~/.bashrc
2012-10-01 08:30:19
User: knoppix5

Any changes to BASH shell made in .bashrc will be active in the current terminal window from the moment you execute this command, ie. aliases, prompt settings etc. No need to restart terminal.

(In BASH 'source' simile to 'eval' lets you generally execute any bunch of commands stacked in a text file).

newgrp -
2012-10-01 10:23:56
User: dendoes
Functions: newgrp

Changes your group to the default group, has the same effect as sourcing your profile/rc file (in any shell) or logging out and back in again.

bashrc-reload() { builtin unalias -a; builtin unset -f $(builtin declare -F | sed 's/^.*declare[[:blank:]]\+-f[[:blank:]]\+//'); . ~/.bashrc; }
2014-03-02 14:24:18
User: Xk2c
Functions: sed unalias unset

Simply sourcing .bashrc does not function correctly when you edit it and change an alias for a function or the other way round with the *same name*.

I therefor use this function. Prior to re-sourcing .bashrc it unsets all aliases and functions.

. ~/.bashrc
2012-10-01 08:41:19
User: DNSpyder

You may want to just use the shortcut "." instead of "source"

. ~/.bashrc

Know a better way?

If you can do better, submit your command here.

What others think

So, I use this often and found a nifty short-cut that saves typing the whole thing.

Thanks to bash history, we can use: ctrl-r followed by the first few characters of the command to recall it from the shell history.

So, assuming you run this in your $HOME with: . ./.bash_profile

you can short-cut this to:

ctrl-r. .

Which cuts it down to just typing 4 characters.

Of course, it depends what is in your shell history.

You may have typed a similar command and you need to check that during the ctrl-r recall.

Comment by mpb 160 weeks and 3 days ago

Your point of view

You must be signed in to comment.