public inbox for cygwin-announce@cygwin.com
 help / color / mirror / Atom feed
From: "Cygwin sed Co-Maintainer" <Brian.Inglis@SystematicSW.ab.ca>
To: "Cygwin Announcements" <cygwin-announce@cygwin.com>
Subject: Updated: sed 4.9
Date: Sun, 13 Nov 2022 14:19:40 -0700	[thread overview]
Message-ID: <20221113141940.30259-1-Brian.Inglis@SystematicSW.ab.ca> (raw)

The following packages have been upgraded in the Cygwin distribution:

* sed	4.9

The sed (Stream EDitor) editor is a stream or batch (non-interactive)
editor. Sed takes text as input, performs an operation or set of
operations on the text, and outputs the modified text. The operations
that sed performs (substitutions, deletions, insertions, etc.) can be
specified in a script file or from the command line.

For more information see the project home pages:

	https://www.gnu.org/software/sed/
	https://sv.gnu.org/projects/sed/

For changes since the previous Cygwin release please see below or read
/usr/share/doc/sed/NEWS after installation; for complete details see:

	/usr/share/doc/sed/ChangeLog
	https://git.sv.gnu.org/gitweb/?p=sed.git;a=shortlog;h=refs/tags/v4.9


Noteworthy changes in release 4.9	2022-11-06

Bug fixes

* 'sed --follow-symlinks -i' no longer loops forever when its operand is
  a symbolic link cycle. [bug introduced in sed 4.2]

* A program with an execution line longer than 2GB can no longer trigger
  an out-of-bounds memory write.

* Using the R command to read an input line of length longer than 2GB
  can no longer trigger an out-of-bounds memory read.

* In locales using UTF-8 encoding, the regular expression '.' no longer
  sometimes fails to match Unicode characters U+D400 through U+D7FF
  (some Hangul Syllables, and Hangul Jamo Extended-B) and Unicode
  characters U+108000 through U+10FFFF (half of Supplemental Private Use
  Area plane B). [bug introduced in sed 4.8]

* I/O errors involving temp files no longer confuse sed into using a
  FILE * pointer after fclosing it, which has undefined behavior in C.

New Features

* The 'r' command now accepts address 0, allowing inserting a file
  before the first line.

Changes in behavior

* Sed now prints the less-surprising variant in a corner case of
  POSIX-unspecified behavior. Before, this would print "n". Now, it
  prints "X":

	printf n | sed 'sn\nnXn'; echo


                 reply	other threads:[~2022-11-13 21:21 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20221113141940.30259-1-Brian.Inglis@SystematicSW.ab.ca \
    --to=brian.inglis@systematicsw.ab.ca \
    --cc=cygwin-announce@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).