Larry Hall (Cygwin) wrote:
On 10/12/2006, Rob Walker wrote:
If you're referring to the performance gain realized, I think it
could have been accomplished (if not as trivially) without breaking
CRLF handling. This seems to be indicated in other posts, ones that
talk about reworking line
On 10/12/2006, Rob Walker wrote:
If you're referring to the performance gain realized, I think it could have
been accomplished (if not as trivially) without breaking CRLF handling.
This seems to be indicated in other posts, ones that talk about reworking
line parsing.
I believe the
Rob Walker wrote:
Matthew Woehlke wrote:
Rob Walker wrote:
Saying cygwin's bash wasn't designed to handle CRLF is a lot like
saying that cygwin's bash (as previously released all these years)
wasn't designed to work with the rest of Windows. This might
actually be the case, but I don't
http://cygwin.com/acronyms/#PPIOSPE, thanks!
Rob Walker wrote:
Matthew Woehlke wrote:
Rob Walker wrote:
Matthew Woehlke wrote:
Rob Walker wrote:
Many, many other cross-platform products make allowances for CRLF
(version control systems are a prime example) to maximize
compatibility, and
On Fri, 13 Oct 2006, Matthew Woehlke wrote:
http://cygwin.com/acronyms/#PPIOSPE, thanks!
Rob Walker wrote:
Matthew Woehlke wrote:
Rob Walker wrote:
Matthew Woehlke wrote:
Rob Walker wrote:
Many, many other cross-platform products make allowances for CRLF
(version
Matthew Woehlke wrote:
http://cygwin.com/acronyms/#PPIOSPE, thanks!
Rob Walker wrote:
Matthew Woehlke wrote:
Rob Walker wrote:
Matthew Woehlke wrote:
Rob Walker wrote:
Many, many other cross-platform products make allowances for CRLF
(version control systems are a prime example) to
Hi!
Installed latest cygwin and I met problems with bash and scripts which are in
DOS format.
$ bash --version
GNU bash, version 3.1.17(9)-release (i686-pc-cygwin)
Copyright (C) 2005 Free Software Foundation, Inc.
I read the mailing lists and I also tried to add ' shopt -s igncr;#' in the
On Thu, Oct 12, 2006 at 03:17:02PM +0300, Antti Tyrv?inen wrote:
Hi!
Installed latest cygwin and I met problems with bash and scripts which are in
DOS format.
$ bash --version
GNU bash, version 3.1.17(9)-release (i686-pc-cygwin)
Copyright (C) 2005 Free Software Foundation, Inc.
I read the
Christopher Faylor wrote:
On Thu, Oct 12, 2006 at 03:17:02PM +0300, Antti Tyrv?inen wrote:
Hi!
Installed latest cygwin and I met problems with bash and scripts which are in
DOS format.
$ bash --version
GNU bash, version 3.1.17(9)-release (i686-pc-cygwin)
Copyright (C) 2005 Free Software
I was writing a similar email when I got Rob's...
I was surprised when all my bash scripts failed after I upgraded
(because of the CR/LF change). One of the most important rules of a
stable product is backwards compatibility. I cannot track down every
bash script and add shopt -s igncr, and
On Thu, Oct 12, 2006 at 01:20:22PM -0700, Rob Walker wrote:
Christopher Faylor wrote:
On Thu, Oct 12, 2006 at 03:17:02PM +0300, Antti Tyrv?inen wrote:
Hi!
Installed latest cygwin and I met problems with bash and scripts which
are in DOS format.
$ bash --version
GNU bash, version
*sigh*
Daniel P. Kionka wrote:
I cannot track down every
bash script and add shopt -s igncr, and no one should ever have to.
Of course not. That is a silly way to deal with the issue. One of the
points of this whole conflagration is to get people to realize that if
they are dealing with
Christopher Faylor wrote:
On Thu, Oct 12, 2006 at 01:20:22PM -0700, Rob Walker wrote:
Christopher Faylor wrote:
On Thu, Oct 12, 2006 at 03:17:02PM +0300, Antti Tyrv?inen wrote:
Hi!
Installed latest cygwin and I met problems with bash and scripts which
are in DOS format.
$
On Thu, Oct 12, 2006 at 07:45:47PM -0700, Rob Walker wrote:
Christopher Faylor wrote:
On Thu, Oct 12, 2006 at 01:20:22PM -0700, Rob Walker wrote:
Christopher Faylor wrote:
On Thu, Oct 12, 2006 at 03:17:02PM +0300, Antti Tyrv?inen wrote:
Installed latest cygwin and I met problems with bash and
Matthew Woehlke wrote:
Rob Walker wrote:
Christopher Faylor wrote:
On Thu, Oct 12, 2006 at 03:17:02PM +0300, Antti Tyrv?inen wrote:
Hi!
Installed latest cygwin and I met problems with bash and scripts
which are in DOS format.
$ bash --version
GNU bash, version 3.1.17(9)-release
Hi all,
i am experiencing problems with the newly introduced shopt igncr to solve
the problem with
CRNL in shell scripts on binary mounts.
Unfortunately this is not working for me at all: I tried all possible places
- first line of the shell script
- $HOME/.bash_profile
- -O igncr at
) -Original Message-
) From: [EMAIL PROTECTED]
) [mailto:[EMAIL PROTECTED] On Behalf Of Frank Illenseer
) Sent: Wednesday, October 04, 2006 3:49 PM
) To: cygwin@cygwin.com
) Subject: shopt igncr not working
)
) Hi all,
)
) i am experiencing problems with the newly introduced shopt
) igncr
Hi Kazuyuki,
thanks for pointing this oiut, but
1) bash version is correct, i.e.
GNU bash, version 3.1.17(9)-release (i686-pc-cygwin)
as recommended
2) I indeed applied the comment character # at the end when using as the
first line of
the shell script
3) When trying the option
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Frank Illenseer on 10/4/2006 2:24 AM:
3) When trying the option of including the shopt line in my
.bash_profile I first opened a
bash login shell (which indeed executes the .bash_profile) and
in-there then ran the script
with
19 matches
Mail list logo
