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.

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

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

Also, 'm' is not a number.

Comment by dbbolton 152 weeks and 6 days ago

Your point of view

You must be signed in to comment.

Related sites and podcasts