Re: [PATCH 2/2] sh-setup: explicitly mark CR as a field separator

From: "Johannes Schindelin" This is the correct thing to do, really: we already specify LF as field separator. Incidentally, this fixes the problem interactive rebase has when the editor wants to save text with CR/LF line endings, as WordPad does in Windows 10.

Re: [PATCH 2/2] sh-setup: explicitly mark CR as a field separator

Hi Philip, On Sun, 25 Oct 2015, Philip Oakley wrote: > From: "Johannes Schindelin" > > @@ -13,7 +13,7 @@ unset CDPATH > > # do not equate an unset IFS with IFS with the default, so here is > > # an explicit SP HT LF. > > Doesn't this comment also need an update,

Re: [PATCH 2/2] sh-setup: explicitly mark CR as a field separator

Hi Brian, re-Cc:ing the Git mailing list. On Sun, 25 Oct 2015, brian m. carlson wrote: > On Sun, Oct 25, 2015 at 01:50:32PM +0100, Johannes Schindelin wrote: > > This is the correct thing to do, really: we already specify LF as > > field separator. > > > > Incidentally, this fixes the problem

[PATCH 2/2] sh-setup: explicitly mark CR as a field separator

This is the correct thing to do, really: we already specify LF as field separator. Incidentally, this fixes the problem interactive rebase has when the editor wants to save text with CR/LF line endings, as WordPad does in Windows 10. Signed-off-by: Johannes Schindelin

shell scripting woes, was Re: [PATCH 2/2] sh-setup: explicitly mark CR as a field separator

Hi Brian, On Sun, 25 Oct 2015, Johannes Schindelin wrote: > On Sun, 25 Oct 2015, brian m. carlson wrote: > > > On Sun, Oct 25, 2015 at 01:50:32PM +0100, Johannes Schindelin wrote: > > > This is the correct thing to do, really: we already specify LF as > > > field separator. > > > > > >