Eric Blake wrote:
According to Matthew Woehlke on 11/2/2006 2:23 PM:
Eric Blake wrote:
And while I'm at it, maybe I will figure out how to name my release
bash-3.1.3-5, so that the bash patchlevel is included in the cygwin
release number.
I thought that was just a matter of what appears in
Eric Blake ebb9 at byu.net writes:
According to David Picton on 10/31/2006 1:12 PM:
Unfortunately I have to report that both versions of bash don't
implement the igncr setting if
commands are read from a sourced file.
Thanks for the report. I'll investigate it, and hopefully bash-3.2-5
Eric Blake wrote:
And while I'm at it, maybe I will figure out how to name my release bash-3.1.3-
5, so that the bash patchlevel is included in the cygwin release number.
I thought that was just a matter of what appears in setup.ini? (But
maybe I am wrong...)
--
Matthew
$ kill bill
kill:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Matthew Woehlke on 11/2/2006 2:23 PM:
Eric Blake wrote:
And while I'm at it, maybe I will figure out how to name my release
bash-3.1.3-
5, so that the bash patchlevel is included in the cygwin release number.
I thought that was
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to David Picton on 10/31/2006 1:12 PM:
Unfortunately I have to report that both versions of bash don't
implement the igncr setting if
commands are read from a sourced file.
Thanks for the report. I'll investigate it, and hopefully
Unfortunately I have to report that both versions of bash don't
implement the igncr setting if
commands are read from a sourced file.
For example, I have /etc/profile set up to issue
shopt -s igncr #
as the first line (or
set -o igncr; export SHELLOPTS #
for version 3.2.4)
If I do
unix2dos
6 matches
Mail list logo
