[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [bug-gawk] gawk 4.1.4: carriage returns not tacitly swollowed

From: arnold
Subject: Re: [bug-gawk] gawk 4.1.4: carriage returns not tacitly swollowed
Date: Thu, 10 Aug 2017 02:55:32 -0600
User-agent: Heirloom mailx 12.4 7/29/08

Eli Zaretskii <address@hidden> wrote:

> > From: "Jannick" <address@hidden>
> > Date: Sat, 29 Jul 2017 10:53:17 +0200
> > 
> > Applying `gawk "/^\\w+$/{print}"` to a CRLF file with simple words in each
> > line prints nothing, i.e. the carriage return is not silently digested by
> > gawk which I would expect it to do and IIRC gawk used to do up some time in
> > the past. Running a LF copy of the CRLF file against this code, emits all
> > lines.
> > 
> > I am just wondering if this should considered a bug, since a line end should
> > always read as '(\r\n|\r|\n)'? I cannot dig into that a little bit more
> > right now, because I am currently not able to clone the git repository
> > (probably due to some savannah issue).
> Doesn't support for CRLF go against the current tendencies in Cygwin
> development to provide a strictly Posix behavior in this regard?
> That's the impression I'm getting from recent discussions of related
> issues on the Cygwin list.
> So please take this up with the Cygwin folks first, and if they agree
> with you, then some Cygwin-specific patch should be in order to fix
> the behavior you are seeing.  If they don't agree with you, then what
> you see is the expected behavior; you should use a native Windows port
> of Gawk if you want CRLF end-of-line to be transparently supported by
> Gawk.

I think Eli's got this exactly right.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]