Williams, Gerald S (Jerry) wrote:
We're you the one who brought up Unicode earlier? Besides,
there are numerous situations where files get transferred
with without needing to involve Windows, so stray
characters occasionally show up here and there. I'm
sure many of us would like support for en
Williams, Gerald S (Jerry) wrote:
Gary R. Van Sickle wrote:
At the risk of being over-obvious, Linux users... use Linux. In such
an insular environment, perhaps they have the luxury of only using
the One True Text File Format (whatever that is).
We're you the one who brought up Unicode earlier
Gary R. Van Sickle wrote:
> At the risk of being over-obvious, Linux users... use Linux. In such
> an insular environment, perhaps they have the luxury of only using
> the One True Text File Format (whatever that is).
We're you the one who brought up Unicode earlier? Besides,
there are numerous si
Hi All...
My $0.02...
If you make igncr the default for bash, I would consider removing the
special handling on the DOS paths.
Thanks for all the work you are doing to speed things up.
Damn the CRs, full speed ahead!
...Karl
From: Eric Blake Subject: Re: Bash and CR/LF line-endings
Date
On Tue, Oct 03, 2006 at 09:24:12PM -0600, Eric Blake wrote:
>According to Gary R. Van Sickle on 10/3/2006 8:27 PM:
>>What's going to break if igncr is simply always on?
>
>Actually, that might not be a bad idea. Those who want literal \r
>would edit cygwin.bat or ~/.bash_profile to turn the shopt
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Gary R. Van Sickle on 10/3/2006 8:27 PM:
>
> What's going to break if igncr is simply always on?
Actually, that might not be a bad idea. Those who want literal \r would
edit cygwin.bat or ~/.bash_profile to turn the shopt off, but leavi
Gary R. Van Sickle wrote:
From: Eric Blake
Sent: Tuesday, October 03, 2006 9:07 PM
Subject: Re: Bash and CR/LF line-endings
[snip]
Perhaps so, but that was a risk I was willing to take, since
cygwin's stated goal is to provide a Linux emulation on
Windows, and Linux users don't g
> From: Eric Blake
> Sent: Tuesday, October 03, 2006 9:07 PM
> Subject: Re: Bash and CR/LF line-endings
>
[snip]
>
> Perhaps so, but that was a risk I was willing to take, since
> cygwin's stated goal is to provide a Linux emulation on
> Windows, and Linux user
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Kazuyuki Hagiwara on 10/3/2006 6:23 PM:
> How about using BASH_ENV variable.
> In the startup script defined by BASH_ENV variable,
> you can put a line "shopt -s igncr".
BASH_ENV already has a defined meaning that conflicts with your
sug
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Pierre Baillargeon on 10/3/2006 12:55 PM:
> I've been wondering during this whole event why one of the original proposal
> was not used?
>
> As far as I can see, the main problem with both latest bash revisions is that
> the solution to t
) -Original Message-
) From: [EMAIL PROTECTED]
) [mailto:[EMAIL PROTECTED] On Behalf Of Pierre Baillargeon
) Sent: Wednesday, October 04, 2006 3:55 AM
) To: cygwin@cygwin.com
) Subject: Bash and CR/LF line-endings
)
) I've been wondering during this whole event why one of the
) ori
I've been wondering during this whole event why one of the original proposal
was not used?
As far as I can see, the main problem with both latest bash revisions is that
the solution to the cr/lf problem demands that users be either pro-active or
gifted guessers. Both the d2u and the shopt solution
12 matches
Mail list logo
