X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Message-ID: <487EB8F5.7020508@cs.cmu.edu>
Date: Wed, 16 Jul 2008 20:13:57 -0700
From: Paul Newell <pnewell AT cs DOT cmu DOT edu>
User-Agent: Thunderbird 2.0.0.14 (Windows/20080421)
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
CC: pnewell AT cs DOT cmu DOT edu
Subject: Re: Freeze with the letter "e"
References: <005101c8e5ef$2ba90220$34ef5248 AT SweetLou> <20080714203321 DOT GC22253 AT ednor DOT casa DOT cgf DOT cx> <487D80AB DOT 5000702 AT cs DOT cmu DOT edu> <20080716145359 DOT GA28882 AT ednor DOT casa DOT cgf DOT cx> <4cee11bc0807161103v79d2c893of1765539f1bd02ad AT mail DOT gmail DOT com> <f60fe000807161133j5ec9f0e1j6a233abfa7ad56cc AT mail DOT gmail DOT com> <20080717005439 DOT GB30298 AT ednor DOT casa DOT cgf DOT cx>
In-Reply-To: <20080717005439.GB30298@ednor.casa.cgf.cx>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

I wish I could say "you caught me" when commenting that I am trying to 
get someone else to do the work for me, but Goggle-ing with your 
suggestions didn't really provide an answer except to clarify that it 
wasn't the letter 'e' ... which was the red herring that had me curious 
enough to take the bait.

Full disclosure, I did not try the Google before I sent my question and, 
yes, that was lazy of me.

Eric Blake's later reply gave me a better clue as to what might be 
happening, thanks.

I've seen the dos vs linux/unix CRLF before but only as a visual 
ickyness inside vim or a caveat when parsing on '\n' expecting a '\0' 
after ... and use dos2unix / unix2dos often. Compiles seem to work under 
RHEL/Fedora gcc and MS VisualStudio without problem, which is the 
majority of interaction between the two along with vim.

I had never heard of the problem jrsyangl described. The "very strange 
results" that Sam Hanes referred to just haven't come up in my 
experience. I'm now more aware of possible issues.

Appreciate all the replies.
Paul


Christopher Faylor wrote:
> On Wed, Jul 16, 2008 at 02:33:08PM -0400, Mark J. Reed wrote:
>   
>> On Wed, Jul 16, 2008 at 2:03 PM, Sam Hanes <elemecca AT gmail DOT com> wrote:
>>     
>>> I think what he's trying to say
>>>       
>> In  Mr. Faylor's his own inimitable way...
>>     
>
> ...he was trying to get someone off their butt to figure it out for
> themselves since it is very far from being a complicated subject and it
> has been discussed before.  google is your friend.  The mailing list
> archives are your friend.
>
> .inputrc shouldn't have CRLF line endings since it causes problems with
> several applications.  I am not cruelly withholding the list of
> applications.  I doubt that anyone has a list.  Just don't use MS-DOS
> line endings in files that are designed to be used on UNIX.
>
> cgf
>
> --
> Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
> Problem reports:       http://cygwin.com/problems.html
> Documentation:         http://cygwin.com/docs.html
> FAQ:                   http://cygwin.com/faq/
>
>
>   


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/