GNU bug report logs - #38706
error

Previous Next

To reply to this bug, email your comments to 38706 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: Garn-Bachmann <garn <at> garn-bachmann.de>
To: bug-sed <at> gnu.org
Subject: error
Date: Sun, 22 Dec 2019 10:37:00 +0100

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

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

From: Assaf Gordon <assafgordon <at> gmail.com>
To: Garn-Bachmann <garn <at> garn-bachmann.de>, 38706 <at> debbugs.gnu.org
Subject: Re: bug#38706: error
Date: Sun, 22 Dec 2019 12:49:48 -0700

tag 38706 moreinfo
stop

Hello,

On 2019-12-22 2:37 a.m., Garn-Bachmann wrote:
>     Inserting characters at the end leads to errors
>     cat ~/te.txt | sed 's|$|h|g'
>     h036
>     h110
>     h110

I suspect this is an issue with end-of-line characters
being "\r\n" (CR LF) in the input file.

The '$' regex matches the end of the line,
which would be AFTER the "\r". The text line becomes "0036\rh\n"
which causes the output you are seeing.

For example:

  $ printf '%s\r\n' aaa bbb ccc | sed 's|$|h|g'
  haa
  hbb
  hcc

---

There are many ways to remove the carriage return (\r) characters.
For example:

Using sed:

  $ printf '%s\r\n' aaa bbb ccc | sed 's|\r|| ; s|$|h|g'
  aaah
  bbbh
  ccch

Using "tr":

  $ printf '%s\r\n' aaa bbb ccc | tr -d '\r' | sed 's|$|h|g'
  aaah
  bbbh
  ccch

Or using the "dos2unix" programs.

---

If this solves the issue - great.
If not, please share the input file (te.txt) to help us
diagnose the issue better.
You can send it to me privately off-list if you prefer.

regards,
 - assaf

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

From: Assaf Gordon <assafgordon <at> gmail.com>
To: Garn-Bachmann <garn <at> garn-bachmann.de>, 38706 <at> debbugs.gnu.org
Subject: Re: bug#38706: error
Date: Tue, 24 Dec 2019 14:36:08 -0700

tag 38706 notabug
close tag 38706
stop

On 2019-12-22 12:49 p.m., Assaf Gordon wrote:
> On 2019-12-22 2:37 a.m., Garn-Bachmann wrote:
>>     Inserting characters at the end leads to errors
>>     cat ~/te.txt | sed 's|$|h|g'
>>     h036
>>     h110
>>     h110
> 
> I suspect this is an issue with end-of-line characters
> being "\r\n" (CR LF) in the input file.

Confirmed off-list that this is indeed the issue,
so I'm closing this as "not a bug".

Discussion can continue by replying to this thread.

regards,
 - assaf

Message #20 received at 38706-done <at> debbugs.gnu.org (full text, mbox):

From: zimoun <zimon.toutoune <at> gmail.com>
To: 38706-done <at> debbugs.gnu.org
Date: Wed, 22 Jan 2020 01:45:33 +0100

close 38706
stop

Dear Assaf,

This bug does not seem related to Guix and the issue seems having been
solved off-list.
Note that "close tag <number>" is not correct to close a bug. Instead,
you need only "close <number>" or send an email to
<number>-done <at> debbugs.gnu.org.

https://debbugs.gnu.org/server-control.html


All the best,
simon

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

From: zimoun <zimon.toutoune <at> gmail.com>
To: 38706 <at> debbugs.gnu.org
Subject: Re:
Date: Wed, 22 Jan 2020 01:52:32 +0100

reopen 38706

Dear Sed developers,


On Wed, 22 Jan 2020 at 01:45, zimoun <zimon.toutoune <at> gmail.com> wrote:

> This bug does not seem related to Guix and the issue seems having been
> solved off-list.

Sorry, I have wrongly filtered out with Debbugs and Emacs.
And this one was related to GNU Sed, not GNU Guix at all.


Well, I think it is not a bug but I am not legitimated at all to close it. :-)
So I reopened it.


> Note that "close tag <number>" is not correct to close a bug. Instead,
> you need only "close <number>" or send an email to
> <number>-done <at> debbugs.gnu.org.
>
> https://debbugs.gnu.org/server-control.html


Sorry again for the confusion.

Regards,
simon

Previous Next

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