Re: Consequences of CRLF in index?
- From
Lars Schneider <larsxschneider@gmail.com>
- Date
- Oct 26, 2017, 11:01 UTC
- Message-ID
- <30ED36AB-FAB1-4635-94AF-FCEC6F02CE01@gmail.com>
- In-Reply-To
- <5e962f69-f9cb-bd7e-481f-050e6239813f@kdbg.org>
Show 10 quoted lines
> On 26 Oct 2017, at 09:09, Johannes Sixt <j6t@kdbg.org> wrote: > > 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.
Wouldn't this kind of .gitattributes setup solve the problem?
* -text *.sh text eol=lf
Thanks, Lars