Buchbinder, Barry (NIH/NIAID) [E] wrote:
> From: Luke Kendall
>>
>> I wonder how many centuries of human endeavour has been
>> absorbed because of the decision to use CR+LF as line
>> endings in DOS?
>>
>
>
> To be fair, \r\n seems to go back to Gary Kildall's CP/M.
> http://en.wikipedia.org/wik
From: Luke Kendall
>
> I wonder how many centuries of human endeavour has been
> absorbed because of the decision to use CR+LF as line
> endings in DOS?
>
To be fair, \r\n seems to go back to Gary Kildall's CP/M.
http://en.wikipedia.org/wiki/Unprintable_characters
--
Unsubscribe info: ht
On 5 Jan, fschmidt wrote:
> > 3. Cygwin text mounts automatically work with either line ending style,
> > because the \r is stripped before bash reads the file. If you absolutely
> > must use files with \r\n line endings, consider mounting the directory
> > where those files live as a text
On 09 January 2007 14:36, Eramo, Mark wrote:
MARK! Please pay attention to the polite requests Eric has made,
particularly this one:
>> -Original Message-
>> From: cygwin-owner AT cygwin DOT com
> ^
>
> http://cygwin.com/acronyms/#PCYMTNQREAIYR - raw
-Original Message-
From: Eric Blake [mailto:[EMAIL PROTECTED]
Sent: Monday, January 08, 2007 11:27 PM
To: cygwin@cygwin.com; Eramo, Mark
Subject: Re: CR/LF problems after upgrade
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
http://cygwin.com/acronyms/#TOFU - reformatted
On Jan 8 21:27, Eric Blake wrote:
> http://cygwin.com/acronyms/#TOFU - reformatted
>
> > -Original Message-
> > From: cygwin-owner AT cygwin DOT com
> ^
>
> http://cygwin.com/acronyms/#PCYMTNQREAIYR - raw email munged
>
> According to Eramo, Mark on 1/8
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
http://cygwin.com/acronyms/#TOFU - reformatted
> -Original Message-
> From: cygwin-owner AT cygwin DOT com
^
http://cygwin.com/acronyms/#PCYMTNQREAIYR - raw email munged
> On 1/5/07, fschmidt wrote:
>> Okay
:[EMAIL PROTECTED] On Behalf
Of DePriest, Jason R.
Sent: Friday, January 05, 2007 5:21 PM
To: cygwin@cygwin.com
Subject: Re: CR/LF problems after upgrade
On 1/5/07, fschmidt wrote:
> Okay, how can I set SHELLOPTS before invoking bash? I tried it in the
> /etc/profile but that didn&
DePriest, Jason R. wrote:
>
> Create a new Windows System Environment variable called SHELLOPTS and set
> it to igncr.
>
Thank you, this worked.
--
View this message in context:
http://www.nabble.com/CR-LF-problems-after-upgrade-tf2924445.html#a8187298
Sent from the Cygwin U
On 1/5/07, fschmidt wrote:
Okay, how can I set SHELLOPTS before invoking bash? I tried it in the
/etc/profile but that didn't work.
--
You admit to not understanding or wanting to understand Unix. What
about Windows?
It took me less than 60 seconds to figure this one out.
Create a new Win
bash,
>>> but you can set it before invoking bash; once in bash, it auto-tracks
>>> the
>>> current state of 'set -o igncr' or 'shopt -s igncr'. If exported, then
>>> all bash child processes inherit the same option settings.
>>>
>
On 05 January 2007 18:45, fschmidt wrote:
> from http://cygwin.com/ml/cygwin-announce/2006-12/msg00026.html
>
>> 2. d2u is your friend. You can use it to convert any problematic script
>> into binary line endings.
>>
>
> Several people I work with, who are even less technical than I am, use
>
how bash
> will treat \r during variable expansion.
>
I don't know what the IFS variable is, or how to use it.
--
View this message in context:
http://www.nabble.com/CR-LF-problems-after-upgrade-tf2924445.html#a8183547
Sent from the Cygwin Users mailing list archive at Nabble.com.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Dave Korn on 1/5/2007 4:43 AM:
> On 05 January 2007 08:33, fschmidt wrote:
>
>> After I upgraded cygwin, my scripts stopped working. I see that this has
>> something to do with a change in how bash treats CR/LF
>
> It's dead simple: j
On 05 January 2007 08:33, fschmidt wrote:
> After I upgraded cygwin, my scripts stopped working. I see that this has
> something to do with a change in how bash treats CR/LF and I see a lot of
> old discussion on this topic, none of which I understand. I am not
> interested in understanding the
I either go back to an old version of cygwin before this change, or can
I add some commands to my /etc/profile to make my scripts work? Any help
would be appreciated.
--
View this message in context:
http://www.nabble.com/CR-LF-problems-after-upgrade-tf2924445.html#a8174573
Sent from the Cygwin
16 matches
Mail list logo