GNU bug report logs - #30336
sed

Previous Next

Package: sed;

Reported by: Roger Adair <adair <at> adinet.com.uy>

Date: Sat, 3 Feb 2018 17:30:01 UTC

Severity: normal

Done: Assaf Gordon <assafgordon <at> gmail.com>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Assaf Gordon <assafgordon <at> gmail.com>
Cc: tracker <at> debbugs.gnu.org
Subject: bug#30336: closed (sed)
Date: Mon, 05 Feb 2018 01:18:02 +0000
[Message part 1 (text/plain, inline)]
Your message dated Sun, 4 Feb 2018 18:17:13 -0700
with message-id <6f3a8d84-be53-2609-6c33-aeff960803ef <at> gmail.com>
and subject line Re: bug#30336: sed
has caused the debbugs.gnu.org bug report #30336,
regarding sed
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)


-- 
30336: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=30336
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems
[Message part 2 (message/rfc822, inline)]
From: Roger Adair <adair <at> adinet.com.uy>
To: bug-sed <at> gnu.org
Subject: sed
Date: Sat, 3 Feb 2018 13:11:04 -0300
Hi,

I'm using Linux Mint 18.3 with sed version

sed (GNU sed) 4.2.2

when I execute the following command:

$ sed 's/c$/7/g' test.data.asc

where the contents of test.data.asc is:

abc  abc
123456

I get the following output:

abc  abc
123456

Whereas I would expect the following:

abc  ab7
123456

If I leave the $ out of the command "ab7 ab7" appears.

What am I doing wrong?  Many thanks for reading my email.

Roger



[Message part 3 (message/rfc822, inline)]
From: Assaf Gordon <assafgordon <at> gmail.com>
To: Roger Adair <adair <at> adinet.com.uy>, 30336-done <at> debbugs.gnu.org
Subject: Re: bug#30336: sed
Date: Sun, 4 Feb 2018 18:17:13 -0700
On 2018-02-03 12:24 PM, Assaf Gordon wrote:
> On 2018-02-03 09:11 AM, Roger Adair wrote:
>> when I execute the following command:
>>
>> $ sed 's/c$/7/g' test.data.asc
>> [...]
> My immediate guess would be that the file has dos/mac line endings
> (e.g. CRLF "\r\n" instead of just line-feed "\n").


Confirmed off-list this is the issue - I'm thus closing this bug.

regards,
 - assaf



This bug report was last modified 7 years and 107 days ago.

Previous Next


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