This is the mail archive of the
cygwin-talk
mailing list for the cygwin project.
Re: suggestion (was Re: 1.7.7: Localization does not follow the language of the OS)
- From: Corinna Vinschen <corinna-cygwin at cygwin dot com>
- To: cygwin-talk at cygwin dot com
- Date: Thu, 13 Jan 2011 14:28:40 +0100
- Subject: Re: suggestion (was Re: 1.7.7: Localization does not follow the language of the OS)
- References: <44682.83.86.0.251.1294773608.squirrel@lavabit.com> <4D2CFAC9.6040706@laposte.net> <20110112095907.GC6353@calimero.vinschen.de> <4D2D7D5D.7080800@gmx.de> <20110112105559.GI6353@calimero.vinschen.de> <4D2DB29D.7010406@gmx.de> <0105D5C1E0353146B1B222348B0411A209BD8DAF7B@NIHMLBX02.nih.gov>
- Reply-to: cygwin-talk at cygwin dot com
- Reply-to: The Vulgar and Unprofessional Cygwin-Talk List <cygwin-talk at cygwin dot com>
On Jan 13 08:07, Buchbinder, Barry (NIH/NIAID) [E] wrote:
> So if one wants to use something that always works, use $(). But when
I disagree, see below...
> `command` works, there is no reason not to use it if one wants to.
> Personally, I still use backticks fairly often.
> (1) On my keyboard, they are significantly easier to type than $().
> (2) It is a habit; $() did not exist when I started to learn scripting.
I use them almost exclusively on the command line, for the simple reason
that I'm using tcsh, which doesn't know the $() syntax. Therefore, from
*my* point of view as a tcsh user, "if one wants to use something that
always works, use backticks ;)
Corinna