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

Create a script of the last executed command

Terminal - Create a script of the last executed command
echo "!!" > foo.sh
2009-02-25 00:37:25
User: dnavarre
Functions: echo
72
Up
Down
Create a script of the last executed command

Sometimes commands are long, but useful, so it's helpful to be able to make them permanent without having to retype them. An alternative could use the history command, and a cut/sed line that works on your platform.

history -1 | cut -c 7- > foo.sh
Add to favourites | Report as malicious

Alternatives

There are 5 alternatives - vote for the best!

Terminal - Alternatives

Know a better way?

If you can do better, submit your command here.

What others think

doesn't work well with quotes in the original command

Comment by rgiar 217 weeks and 5 days ago

@rgiar: Thanks for pointing that out. I came up with a solution, the exact wording of which will vary by system:

history -1 | sed -e 's/^\ [0-9]*\ *//g' > foo.sh

You could make a function out of that, and on top of working properly, it would be simpler and more powerful than my original command.

histecho history -$1 | sed -e 's/^\ [0-9]*\ *//g'
Comment by dnavarre 217 weeks and 3 days ago

You might have better luck using ctrl-x, ctrl-e and then using your editor's "save as" command.

Comment by woxidu 217 weeks and 3 days ago

ctrl-x,ctrl-e just put your present commandline to the texteditor, instead you should use "fc" command which put your last commandline to the texteditor and then you can edit and save, but the question is when you use "fc", the command will be commited after you save, anybody kowns how to save the previous commandline without running it?

Comment by byrgl5 2 days ago

Your point of view

You must be signed in to comment.

Related sites and podcasts