| 1 |
On Thu, 08 Oct 2009 22:34:37 +0300, Nikos Chantziaras wrote: |
| 2 |
|
| 3 |
> >> And it's usually quicker to type with backticks instead of $(): |
| 4 |
> > |
| 5 |
> > But nowhere near as clear. |
| 6 |
> > |
| 7 |
> >> Note: not single-quotes ('), but backticks (`). It's usually the key |
| 8 |
> >> above TAB and to the left of 1. |
| 9 |
> > |
| 10 |
> > I rest my case :) |
| 11 |
> |
| 12 |
> Why? It's one single key. Easy to remember. Nothing is easier than |
| 13 |
> one key instead of needing shift+4-shift+9 to produce "$(" :P |
| 14 |
> |
| 15 |
|
| 16 |
But not as clear as stated above. I've lost count of the number of times |
| 17 |
someone has posted a command, on this list or elsewhere, that uses |
| 18 |
backticks, then had to explain what backticks are after the other person |
| 19 |
used single quotes, not noticing the difference. You even had to explain |
| 20 |
it yourself here, which took a lot more than an extra three keystrokes. |
| 21 |
|
| 22 |
I'm not saying don't use backticks, I occasionally use them myself, |
| 23 |
although I tend to automatically use $( these days, but using them on a |
| 24 |
mailing list only causes confusion. |
| 25 |
|
| 26 |
|
| 27 |
-- |
| 28 |
Neil Bothwick |
| 29 |
|
| 30 |
This tagline SHAREWARE. Send . |
Archives