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

ssh autocomplete

Terminal - ssh autocomplete
complete -W "$(echo `cat ~/.ssh/known_hosts | cut -f 1 -d ' ' | sed -e s/,.*//g | uniq | grep -v "\["`;)" ssh
2009-07-23 15:59:55
User: viner
3
ssh autocomplete

Add to your bash profile to minimize carpal tunnel syndrome.

Doesn't work with user@hostname but appending "-l user" works fine if needed.

Works for ping as well..

complete -W "$(echo `cat ~/.ssh/known_hosts | cut -f 1 -d ' ' | sed -e s/,.*//g | uniq | grep -v "\["`;)" ping

Alternatives

There are 7 alternatives - vote for the best!

Terminal - Alternatives
complete -W "$(echo $(grep '^ssh ' .bash_history | sort -u | sed 's/^ssh //'))" ssh
2009-07-25 23:07:25
User: 0x89
10

Stop tormenting the poor animal cat. See http://sial.org/howto/shell/useless-cat/.

Edit:

replaced

sort | uniq

by

sort -u
perl -ne 'print "$1 " if /^Host (.+)$/' ~/.ssh/config
2011-08-21 14:51:20
User: bashrc
Functions: perl
4

I use this in my bashrc to expand hosts defined in ~/.ssh/config:

function _ssh_completion() {

perl -ne 'print "$1 " if /^Host (.+)$/' ~/.ssh/config

}

complete -W "$(_ssh_completion)" ssh

Here's a great article on how to setup your own ~/.ssh/config:

http://blogs.perl.org/users/smylers/2011/08/ssh-productivity-tips.html

complete -W "$(sed 's/;.*//;' /etc/hosts | awk ' /^[[:digit:]]/ {$1 = "";print tolower($0)}')" ssh
2011-06-20 03:54:45
User: daodennis
0

If you have a lot of hosts in /etc/hosts this would be very useful. Anyone have any more concise examples?

complete -o default -o nospace -W "$(grep -i -e '^host ' ~/.ssh/config | awk '{print substr($0, index($0,$2))}' ORS=' ')" ssh scp sftp
2013-11-19 14:44:41
User: Wamith
Functions: scp ssh
0

I sue this in my .bashrc file

This will also do auto-completion for scp and sftp

complete -W "$(echo $(grep ^Host ~/.ssh/config | sed -e 's/Host //' | grep -v "\*"))" ssh
2014-09-20 19:16:24
User: nathancahill
0

Autocomplete from .ssh/config

Know a better way?

If you can do better, submit your command here.

What others think

Doesn't work very well on a modern SSH system where the known_hosts file is hashed. It's a good idea though.

Comment by ajt 270 weeks and 6 days ago

@ajt to turn off hostname hashing, you may change either /etc/ssh/ssh_config or ~/.ssh/config and change HashKnownHosts from yes to no.

.

The approach shown here is cute, but there is a package in Debian/Ubuntu named 'bash-completion' which extends bash's command completion to help you tab-complete program *arguments*, like ssh hostnames or image/gimp file names when running gimp.

Comment by bwoodacre 270 weeks and 6 days ago

@bwoodacre however the know_hosts file is hashed for a reason - to prevent "bad" scripts from hoping from server to server...

Comment by ajt 270 weeks and 5 days ago

@ajt I read your comment as you saying there was no way to turn off that hashing and so mentioned how to do it. Obviously there is a reason that hashing is turned on by default for added security, but it is still an option that may be turned off by the user if they so choose.

Comment by bwoodacre 270 weeks and 2 days ago

Your point of view

You must be signed in to comment.

Related sites and podcasts