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

type partial command, kill this command, check something you forgot, yank the command, resume typing.

Terminal - type partial command, kill this command, check something you forgot, yank the command, resume typing.
<ctrl+u> [...] <ctrl+y>
2010-07-23 03:33:46
User: claudelepoisson
71
Up
Down
type partial command, kill this command, check something you forgot, yank the command, resume typing.

Example use :

sudo vim /root/bin/

##uh... autocomplete doesn't work...

<ctrl+u> sudo ls /root/bin

##ah! that's the name of the file!

<ctrl+y> sudo vim /root/bin/ ##resume here! Thanks readline!
Add to favourites | Report as malicious

Alternatives

There is 1 alternative - vote for the best!

Terminal - Alternatives
dd [...] p
2010-07-23 23:19:06
User: bartonski
Functions: dd
Tags: bash readline undo key sequence
2
Up
Down
type partial command, kill this command, check something you forgot, yank the command, resume typing.

Use this if you're using vi editing mode.

Example use :

sudo vim /root/bin/ ##uh... autocomplete doesn't work... dd sudo ls /root/bin

##ah! that's the name of the file!

<p> sudo vim /root/bin/ ##resume here! Thanks readline!
Comments (0) | Add to favourites | Report as malicious

Know a better way?

If you can do better, submit your command here.

What others think

Also helpful, for me:

- to have last argument of previous commands in history

- to search history

- for "undo"

Comment by lucafaus 80 weeks ago

This is awesome! I find it useful in combination with (to search history). For some reason when I search for a previous command I often realize I need to do something first before I run it.

Comment by randy909 79 weeks and 2 days ago

Edit to previous comment: I find it useful in combination with ctrl-r (to search history)...

Comment by randy909 79 weeks and 2 days ago

The only downside is that it doesn't show up in your history, and you may override your copy buffer. A slightly safer (albeit more complicated) way to manage this is to do Ctrl-a to take you to the beginning of the line, then put a # (comment character) in front of the command and hit enter. Now you can recall the command through history and modify it by using Ctrl-a to go to the beginning again and remove the #.

Comment by javidjamae 1 week and 2 days ago

Your point of view

You must be signed in to comment.

Related sites and podcasts