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

function to edit your history file

Terminal - function to edit your history file
eh () { history -a ; vi ~/.bash_history ; history -r ; }
2011-03-23 18:00:20
User: unixmonkey8121
Functions: vi
5
Up
Down
function to edit your history file

eh stands for Edit History

.

Frequently, I'll mistype a command, and then step back through my history and correct the command. As a result, both the correct and incorrect commands are in my history file. I wanted a simple way to remove the incorrect command so I don't run it by mistake.

.

When running this function, first the ~/bash_history file is updated, then you edit the file in vi, and then the saved history file is loaded back into memory for current usage.

.

while in vi, remember that `Shift-G` sends you to the bottom of the file, and `dd` removes a line.

.

this command is different than bash built-in `fc` because it does not run the command after editing.

Add to favourites | Report as malicious

Know a better way?

If you can do better, submit your command here.

What others think

I really like this one

Comment by linuxrawkstar 116 weeks and 6 days ago

Wouldn't history -d #, where # is the number of the mistyped command, have been faster more efficient?

Comment by epoch 115 weeks and 6 days ago

`history -d` will work if you know the exact offset and all you wish to do is delete a line. You could do a `history|tail` to be sure of that offset so to not accidentally blow away the wrong command

.

But this function lets you edit your history file too. So you could remove that password from the command line mysql querry. or you could append that successful command with a comment like thus :

.

ssh user@example.com #insert history keyword here

.

It's also faster if you wish to wipe the last ten commands

Comment by unixmonkey8121 115 weeks and 3 days ago

eh () { history -a ; vi + ~/.bash_history ; history -r ; }

.

adding the `+` when evoking `vi` causes the file to open at the very last line. Since you usually want to edit something within say 20 lines of the bottom, this is useful but optional upgrade

Comment by unixmonkey365 78 weeks and 6 days ago

Your point of view

You must be signed in to comment.

Related sites and podcasts