Delete the previous entry in your history
$ ssh root@www1.example.co m ssh: Could not resolve hostname www1.example.co: nodename nor servname provided, or not known $ hackm3! # (Oh crap. I just typed the password on the commandline) $ history |tail ... ... 504 ssh root@www1.example.co m 505 hackm3! # Now it's clear. $ histdel; histdel 503 ssh root@www1.example.co m 504 history |tail
What do you think?
Any thoughts on this command? Does it work on your machine? Can you do the same thing with only 14 characters?
You must be signed in to comment.
What's this?
commandlinefu.com is the place to record those command-line gems that you return to again and again. 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.
Similar Commands
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:
- » all commands
- » commands with 3 up-votes (commandlinefu3)
- » commands with 10 up-votes (commandlinefu10)
alias histdel='history -d $((HISTCMD-1))'Now the clever bit. Add 'histdel' the the list of commands that are ignored by the history:export HISTIGNORE=$HISTIGNORE:hdThis means histdel doesn't need to delete itself from the history and you can still run it as many times as you like. Note: I also have aliases to show my history, which don't add to the history.