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/
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.
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
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:
Suppose that you had change in a directory like /home/user/mycode/code, and now you need to list it, instead of type entire path again, use ls !$ to recall path and list. Useful with many commands, this is only an example. (In this case, same result can be achivied with ls .)
There are 2 alternatives - vote for the best!
If you can do better, submit your command here.
You must be signed in to comment.
duplicate of:
http://www.commandlinefu.com/commands/view/273/use-last-argument-of-last-command
http://www.commandlinefu.com/commands/view/1201/new-command-with-the-last-argument-of-the-previous-command
http://www.commandlinefu.com/commands/view/1397/getting-the-last-argument-from-the-previous-command
I discovered this command by myself today,I don't copied it. ;-)
I think this highlights that it is not so easy for users to search the existing command-line-fu to check if some idea has already been suggested.
"grep the archive" won't always find it.
if you grep for exact command (ls !$) you intend to put down, it's highly unlikely to have a match. However, if you grep the archive more conceptually(e.g use of !$, in this case), then there's better chance to prevent duplications. For instance, if you grep for "!$" there are several entries regarding it.
No one here thinks you "copied" it. This isn't the SATs, it's *nix. It's entirely based on reusing others' code; copying if you will.
What people are trying to bring to your attention, is that there is a fscking search bar readily available. If you would have tried searching for "previous command" or "last parameter" you most certainly would have found the above mentioned duplicates.
I counted 6 by searching a few keywords, and I'm sure I missed a ton.
Ok ;)