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.

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

2011-03-12 - Confoo 2011 presentation
Slides are available from the commandlinefu presentation at Confoo 2011: http://presentations.codeinthehole.com/confoo2011/
2011-01-04 - Moderation now required for new commands
To try and put and end to the spamming, new commands require moderation before they will appear on the site.
2010-12-27 - Apologies for not banning the trolls sooner
Have been away from the interwebs over Christmas. Will be more vigilant henceforth.
2010-09-24 - OAuth and pagination problems fixed
Apologies for the delay in getting Twitter's OAuth supported. Annoying pagination gremlin also fixed.
Hide

Tags

Hide

Functions

Hide

Credits

Site by David Winterbottom (user root).

Make changes in .bashrc immediately available

Terminal - Make changes in .bashrc immediately available
. ~/.bashrc
2012-10-13 09:07:02
User: xamaco
4
Up
Down
Make changes in .bashrc immediately available
Add to favourites | Report as malicious

Alternatives

There are 2 alternatives - vote for the best!

Terminal - Alternatives
source ~/.bashrc
2012-10-01 08:30:19
User: knoppix5
Tags: bash terminal console aliases eval .bashrc
2
Up
Down
Make changes in .bashrc immediately available

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).

Comments (0) | Add to favourites | Report as malicious
newgrp -
2012-10-01 10:23:56
User: dendoes
Functions: newgrp
Tags: terminal console
2
Up
Down
Make changes in any profile available immediately/Change to default group

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.

Comments (0) | Add to favourites | Report as malicious
. ~/.bashrc
2012-10-01 08:41:19
User: DNSpyder
Tags: bash terminal console aliases .bashrc
0
Up
Down
Make changes in .bashrc immediately available

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

Comments (0) | Add to favourites | Report as malicious
. ~/.bashrc
2012-10-02 17:20:29
User: brandizzi
Tags: bash terminal source console aliases eval .bashrc
0
Up
Down
Make changes in .bashrc immediately available
Comments (0) | Add to favourites | Report as malicious

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 28 weeks and 6 days ago

Your point of view

You must be signed in to comment.

Related sites and podcasts