Backticks are evil

echo "The date is: $(date +%D)"
This is a simple example of using proper command nesting using $() over ``. There are a number of advantages of $() over backticks. First, they can be easily nested without escapes: program1 $(program2 $(program3 $(program4))) versus program1 `program2 \`program3 \`program4\`\`` Second, they're easier to read, then trying to decipher the difference between the backtick and the singlequote: `'. The only drawback $() suffers from is lack of total portability. If your script must be portable to the archaic Bourne shell, or old versions of the C-shell or Korn shell, then backticks are appropriate, otherwise, we should all get into the habit of $(). Your future script maintainers will thank you for producing cleaner code.

By: atoponce
2009-03-07 15:51:59

What Others Think

I totally agree.
CodSpirit · 619 weeks and 5 days ago
That's why rc shell uses `{}, $ is too confusing too
maht · 619 weeks and 5 days ago
linuxrawkstar · 619 weeks and 5 days ago
@maht, i agree: echo "The date is: {date +%D}" would be easier. i wish i could do this in bash.
nickleus · 584 weeks and 3 days ago
Bad example; it doesn't need command substitution: date +"The date is %c" (Not to mention that %D is the worst possible date format.)
cfajohnson · 582 weeks and 6 days ago
@cfajohnson cute, but the purpose of the command is to show how to appropriately nest commands, not how to use the date command.
atoponce · 552 weeks and 6 days ago
Yeah, evil but totally necessary. For example, this won't work with $() but works just fine with back ticks: x=1; case $x in 1) echo one ;; esac Why? Because the 1) in the case confuses the $() parser.
zapatar · 415 weeks and 4 days ago
@zapatar, in my FreeBSD, your example runs perfectly in the $() version: $(x=1; case $x in 1) echo ls ;; esac) as well as the backtick version `x=1; case $x in 1) echo ls ;; esac`
brunobiondo · 111 weeks and 2 days ago

What do you think?

Any thoughts on this command? Does it work on your machine? Can you do the same thing with only 14 characters?

You must be signed in to comment.

What's this? is the place to record those command-line gems that you return to again and again. 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.

Share Your Commands

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.


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: