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:
e.g. if rm is aliased for 'rm -i', you can escape the alias by prepending a backslash:
rm [file] # WILL prompt for confirmation per the alias
\rm [file] # will NOT prompt for confirmation per the default behavior of the command
There are 4 alternatives - vote for the best!
A simple directive which disables all aliases and functions for the command immediately following it. Shortcut for the bash built-in 'command' - "command linefoo".
Think, {sic}...
say, someone has aliased ls to 'ls --color=always' and you want to temporarily override the alias (it does not override functions)
If you can do better, submit your command here.
You must be signed in to comment.
This is particularly useful for 'rm', which many distributions insist on aliasing to 'rm -i' (ignoring the bad habits that this inculcates).
I usually type in the full path to the command to make sure I'm using both the unaliased command and also to make sure I'm not launching something out of /usr/local/bin/. Using full paths to commands is also a good habit for any scripts that may run with elevated privileges.
NOTE: Any type of quoting will work: backslash, single quote, double quote.
The Bash Reference Manual says "The first word of each simple command, if unquoted, is checked to see if it has an alias."
Thus, these will all execute the real unaliased rm command:
\rm file'r'm file"r"m file'rm' file"rm" filecommand rm fileThe last example doesn't rely on quoting. Moreover, it will execute the rm command even if your defined rm as a function.
Why not use
command ...or
builtin ...... to make the selection with Bash? This also circumvents aliases and is safe for use in scripts.
Many distributions insist on 'rm -i' only as a root, and it's done for a good reason