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

Equivelant of a Wildcard

Terminal - Equivelant of a Wildcard
2009-08-17 03:56:05
User: matthewbauer
Equivelant of a Wildcard

This is exactly the same as a wildcard - good for times when wildcards are disabled and when you want have a wildcard of a directory that is not your current ({`ls /path/to/dir`}). Does not work on older versions of Bash though.


There are 3 alternatives - vote for the best!

Terminal - Alternatives

Know a better way?

If you can do better, submit your command here.

What others think

are the {} necessary?

Comment by bwoodacre 401 weeks and 5 days ago

if you use backticks often, especially in scripts, it's a good idea to override possible aliases...

Comment by rk299 401 weeks and 5 days ago

According to the bash documentation (for the current version 4.0) aliases are only expanded for "simple commands" http://www.gnu.org/software/bash/manual/bashref.html#Aliases . In my shell, ls is aliased to "ls --color=auto" but if I do

echo {`ls`}

I don't get any color I just get the filenames in curly braces. I think you may be missing files at the beginning and end of the list because if you do:

mkdir testdir; cd testdir touch file{1,2,3,4} ls {`ls`}

then the result is

ls: cannot access {file1: No such file or directory ls: cannot access file4}: No such file or directory file2 file3

so I think you are missing files with with curly braces and should leave them off.

Comment by bwoodacre 401 weeks and 5 days ago

Your point of view

You must be signed in to comment.