This is the mail archive of the
cygwin-apps@sourceware.cygnus.com
mailing list for the Cygwin project.
Re: [stephen.f.tarr@opbu.xerox.com: RE: shell back quote expansion problem]
- To: AJ Reins <tbisp at uswest dot net>
- Subject: Re: [stephen.f.tarr@opbu.xerox.com: RE: shell back quote expansion problem]
- From: Chris Faylor <cgf at cygnus dot com>
- Date: Thu, 29 Jun 2000 11:20:02 -0400
- Cc: Corinna Vinschen <corinna at vinschen dot de>, cygwin-apps at sourceware dot cygnus dot com
- References: <20000626160125.A2960@cygnus.com> <395ACCFA.4D4DB71@pop.mpls.uswest.net>
On Wed, Jun 28, 2000 at 11:13:46PM -0500, AJ Reins wrote:
>Chris Faylor wrote:
>>
>> Do ash and bash open backquoted pipes in text mode? Should they?
>>
>> cgf
>>
>
>Bash appears to let the dll handle that, as setting CYGWIN to binmode
>or nobinmode does have the appropriate affect. This was the reason
>for that particular setting, if memory serves.
I can't think of a reason for not setting a back quoted response to
text mode, though.
When I implemented CYGWIN32=binmode, I was considering the case of
the actual pipe '|' character. I thought that it would be nice to
make this selectable.
I've since come to the conclusion that pipes accessed with '|' should
always be binary since it is just too confusing otherwise. I think
that `` should also always be text. I can imagine a case where it
is vaguely possible that someone would want a \r on their command line
but I'd rather have this use suffer than the much more frequent case
where the \r is not desired.
cgf