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.

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.

Universal configuration monitoring and system of record for IT.

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:



May 19, 2015 - A Look At The New Commandlinefu
I've put together a short writeup on what kind of newness you can expect from the next iteration of clfu. Check it out here.
March 2, 2015 - New Management
I'm Jon, I'll be maintaining and improving clfu. Thanks to David for building such a great resource!

Top Tags



Psst. Open beta.

Wow, didn't really expect you to read this far down. The latest iteration of the site is in open beta. It's a gentle open beta-- not in prime-time just yet. It's being hosted over at UpGuard (link) and you are more than welcome to give it a shot. Couple things:

  • » The open beta is running a copy of the database that will not carry over to the final version. Don't post anything you don't mind losing.
  • » If you wish to use your user account, you will probably need to reset your password.
Your feedback is appreciated via the form on the beta page. Thanks! -Jon & CLFU Team

escape any command aliases

Terminal - escape any command aliases
2009-02-11 19:34:21
User: wwest4
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


There are 5 alternatives - vote for the best!

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

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

2012-01-05 00:35:49
User: libdave

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

2015-01-15 18:31:50
User: tyzbit

Most distributions alias cp to 'cp -i', which means when you attempt to copy into a directory that already contains the file, cp will prompt to overwrite. A great default to have, but when you mean to overwrite thousands of files, you don't want to sit there hitting [y] then [enter] thousands of times.

Enter the backslash. It runs the command unaliased, so as in the example, cp will happily overwrite existing files much in the way mv works.

2011-05-06 15:45:31
User: panlm

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 419 weeks and 6 days 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 267 weeks and 6 days 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 267 weeks and 5 days ago

Why not use

command ...


builtin ...

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

Comment by assarbad 262 weeks ago

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

Comment by OutputLogic 249 weeks and 1 day ago

Your point of view

You must be signed in to comment.