Subject: Re: bug: cygwin/bash: echo > %ED does wrong thing
From: Chris Faylor <[email-masked]>
To: Steve Morris <[email-masked]>
Cc: [email-masked]
Date: Sun, 16 May 1999 00:54:14 -0400

On Sat, May 15, 1999 at 11:57:14AM -0700, Steve Morris wrote:
>"echo >%ED" creates the wrong file. The %E gets expanded to "error 2".

>>Date: Fri, 14 May 1999 23:59:39 -0400
>>To: Steve Morris <[email-masked]>
>>Subject: Re: error string substituted for %E in filename
>>Message-ID: <[email-masked]>
>>References: <[email-masked]>
>>Mime-Version: 1.0
>>Content-Type: text/plain; charset=us-ascii
>>X-Mailer: Mutt 0.95.3i
>>In-Reply-To: <[email-masked]>; from Steve Morris on Fri, May 14, 1999 at 08:21:24PM -0700
>>Status: RO
>>Content-Length: 462
>>Lines: 12
>>
>>On Fri, May 14, 1999 at 08:21:24PM -0700, Steve Morris wrote:
>>>Why does this program create a file named ".new.error 2D.1".  That
>>>surely wasn't my intention and is croaking cvs client when checking
>>>out a file called "%ED.1". Obviously something thinks "%E" should be
>>>expanded to the current error string but in the open command? Not what
>>>I would have expected.
>>>
>>>Do I have to quote % to work around this?
>>
>>It's a bug in 20.1, fixed in later snapshots.
>>
>>cgf

--
Want to unsubscribe from this list?
Send a message to [email-masked]