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.


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

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!
Hide

Top Tags

Hide

Functions

Psst. Open beta.

Wow, didn't really expect you to read this far down. The latest iteration of the site is in open beta. It's a gentle open beta-- not in prime-time just yet. It's being hosted over at UpGuard (link) and you are more than welcome to give it a shot. Couple things:

  • » The open beta is running a copy of the database that will not carry over to the final version. Don't post anything you don't mind losing.
  • » If you wish to use your user account, you will probably need to reset your password.
Your feedback is appreciated via the form on the beta page. Thanks! -Jon & CLFU Team

Execute the command given by history event number

Terminal - Execute the command given by history event number
!<number>
2011-08-18 01:08:57
User: dbbolton
0
Execute the command given by history event number

You can find a command's history event number via the `history` command.

You can also put the history event number in your prompt: \! for bash, or %h for zsh.

Finally, I would like to point out that by "number", I mean POSITIVE INTEGER. Not, say, a letter, such as 'm'. Examples:

!1

or

!975

Alternatives

There are 3 alternatives - vote for the best!

Terminal - Alternatives

Know a better way?

If you can do better, submit your command here.

What others think

Actually, this will only execute the most recent executed, so where does the "number" come into play?

2997 mail -s test jj

2998 exit

2999 history

!m will execute 2997

Comment by Habitual 262 weeks ago

Did you even read the description? !! returns the previous command.

zsh

% PROMPT='%h %% ' 1012 % echo "This is history event number 1012" This is history event number 1012 1013 % history | tail -n 2 1011 PROMPT='%h %% ' 1012 echo "This is history event number 1012" 1014 % !1012 echo "This is history event number 1012" This is history event number 1012 1015 %

bash

history | tail -n 2 1003 echo "This is history event 1003" 1004 history | tail -n 2 !1003 echo "This is history event 1003" This is history event 1003
Comment by dbbolton 262 weeks ago

Other resources that confirm my command is correct:

http://www.talug.org/events/20030709/cmdline_history.html

http://www.catonmat.net/blog/the-definitive-guide-to-bash-command-line-history/

I recommend against down-voting a command unless you know what you're talking about.

Comment by dbbolton 262 weeks ago

Also, 'm' is not a number.

Comment by dbbolton 262 weeks ago

Your point of view

You must be signed in to comment.