Mail Archives: cygwin/2006/10/25/08:04:40
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
http://cygwin.com/acronyms/#PPIOSPE - redirecting to the list.
According to Bruun, Peter Michael (HP C&I CME OSS CoE) on 10/25/2006 1:18 AM:
> Hello Eric,
>
> Thanks for the thorough explanation.
>
> Yes, the missing handling of CRLF in `` and $() is the point of my
> message - these should understand the igncr setting.
>
> Adding d2u is a cludge - I am working in a cross-platform environment
> and I do not have d2u on all platforms. I could define it as a dummy
> shell-function, but I don't want my Unix scripts to be unnecessarily
> polluted by such things. I believe it is an essential part of the
> purpose of Cygwin is to hide Windows specific detals, and so having to
> pollute my scripts in this way defies the purpose of Cygwin.
>
> Adding --text to cat is similarly a cludge and would not be portable to
> native Unix platforms.
>
> For now, setting IFS sounds like the best option, but as far as I can
> see, it does not affect command substitution either (at the moment of
> writing I only have access to bash-3.1-6).
>
> In some contexts I already do white-space normalization using something
> like this:
>
> F=`echo \`cat f.txt\``
>
> With IFS set, this will work, but the method is only correct if f.txt
> does not contain significant white-space other than single blank
> characters.
>
> So I am looking forward to bash-3.2-4 with igncr support in command
> substitution. When do you think, it will be around?
Yesterday evening.
>
> Best regards,
>
> Peter Michael Bruun (HP C&I CME OSS CoE)
>
- --
Life is short - so eat dessert first!
Eric Blake ebb9 AT byu DOT net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.1 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFFP1Lq84KuGfSFAYARAnIhAJ9qUqcC1vCqbmM2WjPkKm6MB+wwwACaA6QJ
RyzGNJpf4hZxaAUTFUAtk5A=
=La/N
-----END PGP SIGNATURE-----
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
- Raw text -