Re: bin/50111: sed does not support \n newline in replacement patterns.

[David Holland <dholland-bugs%netbsd.org@localhost>]

The following reply was made to PR bin/50111; it has been noted by GNATS.

From: David Holland <dholland-bugs%netbsd.org@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: 
Subject: Re: bin/50111: sed does not support \n newline in replacement
 patterns.
Date: Sun, 2 Aug 2015 19:41:11 +0000

 On Sun, Aug 02, 2015 at 04:15:01AM +0000, Christos Zoulas wrote:
  >  most sed implementations, don't recognize \n. It is always easier for
  >  us to fix a PR when there is patch with it. Otherwise we have to do most
  >  of the work, and adding \n to sed, might not be our highest priority.
 
 I kind of agree with the OP in this one: there is no downside to
 supporting \n. It should be a small localized change, and it doesn't
 create any new incompatibilities; that is, \n in the replacement side
 of a sed substitution isn't otherwise meaningful.
 
 There is a can of worms, though, which is that it should also support
 \t... and \r... and then what about \b, \a, or even \f and \v?
 
 in any event sending in a patch will make it happen much faster.
 
 -- 
 David A. Holland
 dholland%netbsd.org@localhost