Write on the console without being registered

history -d $((HISTCMD-1)) && command_to_run
Sample Output
root@ubuntu1204:~# history -d $((HISTCMD-1)) && fdisk
Usage:
 fdisk [options] <disk>    change partition table
 fdisk [options] -l <disk> list partition table(s)
 fdisk -s <partition>      give partition size(s) in blocks

Options:
 -b <size>             sector size (512, 1024, 2048 or 4096)
 -c[=<mode>]           compatible mode: 'dos' or 'nondos' (default)
 -h                    print this help text
 -u[=<unit>]           display units: 'cylinders' or 'sectors' (default)
 -v                    print program version
 -C <number>           specify the number of cylinders
 -H <number>           specify the number of heads
 -S <number>           specify the number of sectors per track

root@ubuntu1204:~# history | tail -n4
  692  cd
  693  echo $HISTCMD
  694  history -d 694
  695  history | tail -n4
root@ubuntu1204:~# 

2
By: bleiva
2013-02-01 15:06:08

1 Alternatives + Submit Alt

What Others Think

This can be done also by preceding the command with a whitespace. pwd # is logged to history pwd # is not logged
reeloo · 297 weeks ago
This can be done also by preceding the command with an extra whitespace. $ pwd # is logged to history $ pwd # is not logged
reeloo · 297 weeks ago
This can be done also by preceding the command with a whitespace. ;)
reeloo · 297 weeks ago
This can be done also by preceding the command with an extra whitespace.
reeloo · 297 weeks ago
preceding the command with a whitespace didn't work on centos 5/6
bunam · 297 weeks ago
IF you're using bash AND you have either 'ignorespace' in $HISTCONTROL, or $HISTIGNORE with a whitespace character in it, THEN bash won't save to the command history any commands that start with whitespace. Maybe blevia offered this suggestion for people who aren't using bash but some other shell that has a 'history' command?
Mozai · 296 weeks and 2 days ago

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.

Share Your 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: