Larry Breyer ucsd.edu> writes:
> I am a bit confused by these numbering schemes. When I look at the
> 'Select Packages' section of setup, my choices for bash are 3.1-6 or
> 3.1-8. I assumed they were shorthand for 3.1.16 and 3.1.18.
Nope, they are shorthand for 3.1.17(6) and 3.1.17(8). Everyt
Eric Blake wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Larry Breyer on 9/27/2006 3:22 PM:
What changed from bash 3.1.17 to 3.1.18 ?
I don't know, but let me know when you find out :)
(There is no 3.1.18 - the latest official bash is 3.1.17, at cygwin
release 8, but ups
Eric Blake wrote:
According to Eric Blake on 9/27/2006 7:02 PM:
change the script to ignore whitespace (make the first non-comment line
set IFS appropriately, as in this snippet:
IFS=' ''''
'
I retract this third suggestion. On investigation of the bash source,
bash still treats \r as
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Eric Blake on 9/27/2006 7:02 PM:
> change the script to ignore whitespace (make the first non-comment line
> set IFS appropriately, as in this snippet:
> IFS=' '' ''
> '
I retract this third suggestion. On investigation of the bash
Christopher Faylor wrote:
On Wed, Sep 27, 2006 at 05:58:15PM -0400, Larry Hall (Cygwin) wrote:
Ah. Blindly doing *anything* and then blaming others for the results is
not a recipe for sympathy.
I think that one is going in my "quotes" file.
I am honored. :-)
--
Larry Hall
On Wed, Sep 27, 2006 at 05:58:15PM -0400, Larry Hall (Cygwin) wrote:
>Ah. Blindly doing *anything* and then blaming others for the results is
>not a recipe for sympathy.
I think that one is going in my "quotes" file.
cgf
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Larry Breyer on 9/27/2006 3:22 PM:
> What changed from bash 3.1.17 to 3.1.18 ?
I don't know, but let me know when you find out :)
(There is no 3.1.18 - the latest official bash is 3.1.17, at cygwin
release 8, but upstream is very unlikely
mwoehlke wrote:
Larry Breyer wrote:
What changed from bash 3.1.17 to 3.1.18 ?
Did you bother reading the ANNOUNCEMENT?
Right. This is *not* a bug. It's a feature. If you read the ANNOUNCEMENT
on the ANOUNCEMENT list (copied to the Cygwin list as well), it would be
obvious to you why you'
Larry Breyer wrote:
What changed from bash 3.1.17 to 3.1.18 ?
Did you bother reading the ANNOUNCEMENT?
I blindly performed a cygwin update, rebooted, and attempted startx.
X came up OK but the terminals would not respond to keyboard input.
Looking at the output of startx it became apparent so
9 matches
Mail list logo
