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.

OpenID
or
Sign in Register

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

Hide

Credits

Site by David Winterbottom (user root).

Equivelant of a Wildcard

Terminal - Equivelant of a Wildcard
`ls`
2009-08-17 03:56:05
User: matthewbauer
0
Up
Down
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.

Add to favourites | Report as malicious

Alternatives

There are 9 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 200 weeks and 1 day ago

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

Comment by rk299 200 weeks and 1 day 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 200 weeks ago

Your point of view

You must be signed in to comment.

Related sites and podcasts