From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: sed match DOS end of line
Date: Thu, 27 Jun 2013 14:49:00 -0000 [thread overview]
Message-ID: <20130627142405.GA2378@calimero.vinschen.de> (raw)
In-Reply-To: <01E9402441FFBB4BBEA0A82549A7D94A0C27C5@ORD2MBX02C.mex05.mlsrvr.com>
On Jun 27 13:28, Paul Becker wrote:
> > From: On Behalf Of Corinna Vinschen
> > Sent: Thursday, June 27, 2013 6:49 AM
> > Subject: [ANNOUNCEMENT] Updated: sed-4.2.2-2
> >
> > I've just updated the Cygwin 32 and 64 bit version of sed to 4.2.2-2.
>
> Since this 'sed' change, I noticed that "$" does not match a dos formatted file end-of-line anymore.
>
> example:
> echo "endofline^M" | sed "s/e$/X/"
>
> sed 4.2.1 returns
> endoflinX
>
> sed 4.2.2 returns
> endofline
This seems to be an upstream change. The Cygwin 4.2.1 and 4.2.2
releases are build the same way. 4.2.1-2 (-3 on 64 bit) and 4.2.2-1 are
both built from just the vanilla upstream sources.
While 4.2.2-2 adds the latest upstream gnulib regex, it behaves
otherwise identically to 4.2.2-1. And both 4.2.2 releases show the same
behaviour in terms of CRLF line endings.
But it's really puzzeling. There's no indication for this change
in the sources.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2013-06-27 14:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-27 14:24 Paul Becker
2013-06-27 14:49 ` Corinna Vinschen [this message]
2013-06-27 15:16 ` autoreconf/gettext puzzle (was Re: sed match DOS end of line) Corinna Vinschen
2013-06-27 15:42 ` Corinna Vinschen
2013-06-27 15:51 ` Yaakov (Cygwin/X)
2013-06-27 15:55 ` Corinna Vinschen
2013-06-27 17:31 ` Corinna Vinschen
2018-01-07 0:25 sed match DOS end of line Steve Harlow
2018-01-07 2:16 ` Steven Penny
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130627142405.GA2378@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).