GNU bug report logs - #59599
Possible sed bug

Previous Next

To reply to this bug, email your comments to 59599 AT debbugs.gnu.org.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: John Larew <john.larew <at> outlook.com>
To: "bug-sed <at> gnu.org" <bug-sed <at> gnu.org>
Subject: Possible sed bug
Date: Sat, 26 Nov 2022 00:05:53 +0000

[Message part 1 (text/plain, inline)]

I have to admit to little time using the tool. To my admittedly limited knowledge, this appears to be a bug:

[Reputation: Disabled]
sed with wildcard matching
________________________________
I have a DOS file with several record sequences as follows:

...
Online
1234 Main St
Anytown
...

I'm trying to edit the file with the following sed command;

sed -z 's/Online\r\n\(.*\)\r\n\(.*\)/Online\r\n\1 \2/g' test.txt

but there is no change in the stdout stream, much to my surprise.

Thanks in advance for any insight you can provide.

I am trying to remove the newline after the 2nd record following "Online", a street address.

I have verified the file contents using sed --debug functionality.

I have since solved the problem with an alternate sed programming methodology.

sed --version reports 4.9.

Thanks for your time and consideration.


John Larew
860-917-0225
John.Larew <at> outlook.com

[Message part 2 (text/html, inline)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.