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

escape any command aliases

Terminal - escape any command aliases
\[command]
2009-02-11 19:34:21
User: wwest4
83
escape any command aliases

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

Alternatives

There is 1 alternative - vote for the best!

Terminal - Alternatives
\foo
2011-09-23 11:00:35
User: egreSS
Tags: alias
19

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

\ls
2012-01-05 00:35:49
User: libdave
5

say, someone has aliased ls to 'ls --color=always' and you want to temporarily override the alias (it does not override functions)

\<command>
2011-05-06 15:45:31
User: panlm
-1

if you have a alias like this:

alias cp='cp -i'

# cp file1 file1.bak

equal to

# cp -i file1 file1.bak

(it will not overwrite file1.bak if it exist)

# \cp file1 file1.bak

equal to

# /bin/cp file1 file1.bak

(skip alias settings, it will overwrite file1.bak if it exist)

Know a better way?

If you can do better, submit your command here.

What others think

This is particularly useful for 'rm', which many distributions insist on aliasing to 'rm -i' (ignoring the bad habits that this inculcates).

Comment by mkc 298 weeks and 1 day ago

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.

Comment by Mozai 146 weeks ago

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" file command rm file

The last example doesn't rely on quoting. Moreover, it will execute the rm command even if your defined rm as a function.

Comment by Robin 146 weeks ago

Why not use

command ...

or

builtin ...

... to make the selection with Bash? This also circumvents aliases and is safe for use in scripts.

Comment by assarbad 140 weeks and 2 days ago

Many distributions insist on 'rm -i' only as a root, and it's done for a good reason

Comment by OutputLogic 127 weeks and 3 days ago

Your point of view

You must be signed in to comment.

Related sites and podcasts