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.

World cup college
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

2009-09-12 - Email updates now available
You can now enable email updates to let you know each time you're command is commented on.
2009-07-11 - API and javascript blog widget now available
A simple API has been released, allowing commands to be retrieved in various formats. This also allows commands to be embedded on blogs/homepages.
2009-05-17 - Added duplicate suggestions to the new command form
When adding a new command, a quick background search is performed to make sure you're not duplicating a command already in the system.
2009-05-17 - Now using Gravatars for comments
Comments now display users' gravatars with the default setting as a random monster.
Hide

Tags

Hide

Functions

ssh autocomplete

Terminal - ssh autocomplete
complete -W "$(echo `cat .bash_history | egrep '^ssh ' | sort | uniq | sed 's/^ssh //'`;)" ssh
2009-07-24 09:48:46
User: kulor
-2
ssh autocomplete

Could use your ssh bash history if your known_hosts are hashed and you want to keep it hashed

Alternatives

There are 2 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
6

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

Edit:

replaced

sort | uniq

by

sort -u
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
4

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

Know a better way?

If you can do better, submit your command here.

What others think

or you could set your hosts in .ssh/config

Comment by svg 28 weeks and 3 days ago

You just blew the purpose of a hashed known_hosts files with the history. It may protect you against bots, thats all.

Comment by oernii2 28 weeks and 3 days ago

Your point of view

You must be signed in to comment.

Related sites and podcasts