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.

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:



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.




Capitalize first letter of each word in a string

Terminal - Capitalize first letter of each word in a string
read -ra words <<< "<sentence>" && echo "${words[@]^}"
2011-09-10 02:46:42
User: RanyAlbeg
Functions: echo read
Capitalize first letter of each word in a string

I find it useless but definitely simpler than #9230


There is 1 alternative - vote for the best!

Terminal - Alternatives
command <<< word
2012-02-29 03:14:54
User: adeverteuil
Functions: command
Tags: bash stdin

Don't do this:

echo word | command

Using a bash "here strings" and "here documents" look leeter than piping echo into the command. Also prevents subshell execution. Word is also expanded as usual.

echo 'fOo BaR' | tr '[A-Z]' '[a-z]' | sed 's/\(^\| \)\([a-z]\)/\1\u\2/g'
2011-09-09 21:40:31
User: caiosba
Functions: echo sed tr
Tags: sed tr capitalize

Capitalize first letter of each word in a string.

ruby -ne 'puts $_.split.collect(&:capitalize).join(" ")' <<< "pleAse cOuld YOu capiTalizE Me"
2011-09-15 01:04:43
User: Quiryaki

"-n" loops around ; "-e" executes the given quoted string ; "$_" is the current line ; "split" creates an array on white space; each item of the array is "collected" to be then "capitalized" ; the array is "joined" back into a string.

echo 'fOo BaR' | ruby -e "p STDIN.gets.split.map(&:capitalize).join(' ')"

Know a better way?

If you can do better, submit your command here.

What others think

I get

sh: Syntax error: redirection unexpected

when I try this command.

Comment by Mozai 184 weeks and 5 days ago

9230 and 9232 make the first letter of each word capital AND the subsequent letters lower case. Your alternative leaves the subsequent letters capital. In other words theirs converts 'fOo baR' to 'Foo Bar' and yours converts to 'FOo BaR'.

Comment by splante 184 weeks and 2 days ago

Your point of view

You must be signed in to comment.