From: Johannes Sixt <j6t@kdbg.org>
Date: Thu, 26 Oct 2017 07:09:27 GMT
Subject: Re: Consequences of CRLF in index?
Message-ID: <5e962f69-f9cb-bd7e-481f-050e6239813f@kdbg.org>
In-Reply-To: <alpine.DEB.2.21.1.1710251415040.6482@virtualbox>

Am 25.10.2017 um 14:19 schrieb Johannes Schindelin:
> I envy you for the blessing of such a clean C++ source that you do not
> have any, say, Unix shell script in it. Try this, and weep:
> 
> 	$ printf 'echo \\\r\n\t123\r\n' >a1
> 
> 	$ sh a1
> 
> 	a1: 2: a1: 123: not found

I was bitten by that, too. For this reason, I ensure that shell scripts 
and Makefiles begin their life on Linux. Fortunately, modern editors on 
Windows, includ^Wand vi, do not force CRLF line breaks, and such files 
can be edited on Windows, too.

Of course, I do not set core.autocrlf anywhere to avoid any changes 
behind my back.

> For the same reason (Unix shell not handling CR/LF gracefull), I went
> through that painful work that finally landed as 00ddc9d13ca (Fix build
> with core.autocrlf=true, 2017-05-09).

That's much appreciated!

-- Hannes