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

I hate `echo X | Y`

Terminal - I hate `echo X | Y`
base64 -d <<< aHR0cDovL3d3dy50d2l0dGVyc2hlZXAuY29tL3Jlc3VsdHMucGhwP3U9Y29tbWFuZGxpbmVmdQo=
2009-03-27 23:20:23
User: stu
15
Up
Down
I hate `echo X | Y`

apart from not being generalisable to all shells, `Y <<< X` seems nicer to me than `echo X | Y`, e.g.

&lt;&lt;&lt; lol cat;

it reads easier, you type less, and it also looks cool

Add to favourites | Report as malicious

Alternatives

There is 1 alternative - vote for the best!

Terminal - Alternatives
command <<< word
2012-02-29 03:14:54
User: claudelepoisson
Functions: command
Tags: bash stdin
8
Up
Down
This is how you should push a string in a command's 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.

Comments (2) | Add to favourites | Report as malicious

Know a better way?

If you can do better, submit your command here.

What others think

It seems that every day I learn a new operator in bash. I'm not sure if this is a good or bad thing, but it delights me every time! Thanks for this!

Comment by isaacs 216 weeks and 3 days ago

I tested it on my Fedora system: Works with bash, mksh, and zsh, does not work with csh and tcsh.

Comment by penpen 216 weeks and 3 days ago

if you care about keystrokes put

alias e=echo

in your .bashrc

while you're at it pop alias

en='echo -n'

in there too

doesn't work for in='

Comment by maht 216 weeks and 3 days ago
in='<<<'
Comment by maht 216 weeks and 3 days ago

Doesn't work in bash-invoked-as-sh, so it's something you need to remember doesn't work in #!/bin/sh scripts... doesn't work in dash either (basically, "not in POSIX at all")

Comment by eichin 200 weeks and 5 days ago

Your point of view

You must be signed in to comment.

Related sites and podcasts