On Tue, 13 Feb 2007 00:56:24 Eric Backus wrote:
>
> Obviously, the horse is still alive and attempting to limp along. I predict
> it'll stay alive for quite some time longer.
>
[snip]
>
> * Workaround inserting "set -o igncr" is impractical when there are lots of
> scripts.
[snip]
Among my many
I would like to thank those who unselfishly took their time to help us and
anyone else who reads these posts in the future, as the situation may
persist for a while.
Also, we do appreciate that open source developers are not paid, and do
their best. It's great this group is so active. It impress
> * Workaround by exporting SHELLOPTS breaks things because it put interactive
> things like history expansion into non-interactive shells (try calling "man
> bash" after exporting SHELLOPTS with igncr, for example).
Quit spreading FUD. I fixed this in bash 3.2.9-11, due to user
requests on thi
Eric Backus wrote:
Matthew Woehlke users.sourceforge.net> writes:
Dennis Simpson wrote:
Three of us updated to latest windows cygwin last week, and none can run
even simple .sh scripts any more. Prior version was 6 months ago.
http://cygwin.com/ml/cygwin-announce/2006-12/msg00026.html
Next
Matthew Woehlke users.sourceforge.net> writes:
> Dennis Simpson wrote:
> > Three of us updated to latest windows cygwin last week, and none can run
> > even simple .sh scripts any more. Prior version was 6 months ago.
>
> http://cygwin.com/ml/cygwin-announce/2006-12/msg00026.html
>
> Next time
Dennis Simpson wrote:
Three of us updated to latest windows cygwin last week, and none can run
even simple .sh scripts any more. Prior version was 6 months ago.
http://cygwin.com/ml/cygwin-announce/2006-12/msg00026.html
Next time RTFRA. Oh, and STFLA; this particular horse died a *lng*
t
6 matches
Mail list logo
