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

Converts uppercase chars in a string to lowercase

Terminal - Converts uppercase chars in a string to lowercase
s="StrinG"; echo ${s,,}
2010-08-12 16:02:38
User: karpoke
Functions: echo
Converts uppercase chars in a string to lowercase

Another alternative is to define a function:

lower() {

echo ${@,,}


lower StrinG


There is 1 alternative - vote for the best!

Terminal - Alternatives
echo StrinG | tr '[:upper:]' '[:lower:]'
echo StrinG | tr 'A-Z' 'a-z'
2010-08-12 15:42:56
User: randy909
Functions: echo tr

Another way to do it with slightly fewer characters. It doesn't work on Russian characters; please don't vote down because of that. :p It's very handy for those of us working in ascii :)

Know a better way?

If you can do better, submit your command here.

What others think

I'm getting:

-bash: ${s,,}: bad substitution

What is that trick? That syntax is foreign to me.

Comment by randy909 315 weeks and 2 days ago

I don't know why you get that "bad substitution". Are you running the bash shell or is it another one? I'm running bash v4.1.5.

This is a case of paremeter expansion of the form ${parameter,,pattern}. The , operator converts each matching uppercase letters to lowercase. When the pattern is omitted, it is treated like a ?, which matches every character.

More info in the section of "Parameter expansion" in the bash man page.

Comment by karpoke 315 weeks and 2 days ago

GNU bash, version 3.2.49(23)-release

Doesn't look like it supports the , operator. I tried to figure out another way to do it with parameter expansion in 3.2 but I couldn't see a way. Parameter expansion looks cool though, thanks for the help!

Comment by randy909 315 weeks and 2 days ago

its bash 4 syntax.

to uppercase conversion:

s="Test" ; echo ${s^^}

Comment by unefunge 301 weeks and 2 days ago

Your point of view

You must be signed in to comment.