GNU bug report logs - #36202
Add example of how to write the two addresses

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 36202 in the body.
You can then email your comments to 36202 AT debbugs.gnu.org in the normal way.

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

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

From: Dan Jacobson <jidanni <at> jidanni.org>
To: bug-sed <at> gnu.org
Subject: Add example of how to write the two addresses
Date: Thu, 13 Jun 2019 19:33:15 +0800

(info "(sed) Other Commands") says many times

     As a GNU extension, this command accepts two addresses.

You need to give an example of how to write the two addresses!

You invent an extension, so only you know how to use it. One cannot look
the usage up elsewhere.

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

From: Eric Blake <eblake <at> redhat.com>
To: Dan Jacobson <jidanni <at> jidanni.org>, 36202 <at> debbugs.gnu.org
Subject: Re: bug#36202: Add example of how to write the two addresses
Date: Thu, 13 Jun 2019 21:28:50 -0500

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

On 6/13/19 6:33 AM, Dan Jacobson wrote:
> (info "(sed) Other Commands") says many times
> 
>      As a GNU extension, this command accepts two addresses.
> 
> You need to give an example of how to write the two addresses!
> 
> You invent an extension, so only you know how to use it. One cannot look
> the usage up elsewhere.

info "(sed) Addresses overview" says:

   An address range is specified with two addresses separated by a comma
(',').  Addresses can be numeric, regular expressions, or a mix of both.

The extension is not how to write two addresses (since POSIX already
requires several commands such as 's' to do so), but that GNU sed
extends the set of commands that take two addresses (where POSIX only
requires the command to take 1).

I think the information you are requesting is already present in the
manual, so it is now a judgment call on whether it can be improved; are
you volunteering to write a patch?

-- 
Eric Blake, Principal Software Engineer
Red Hat, Inc.           +1-919-301-3226
Virtualization:  qemu.org | libvirt.org

[signature.asc (application/pgp-signature, attachment)]

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

From: 積丹尼 Dan Jacobson <jidanni <at> jidanni.org>
To: Eric Blake <eblake <at> redhat.com>
Cc: 36202 <at> debbugs.gnu.org
Subject: Re: bug#36202: Add example of how to write the two addresses
Date: Fri, 14 Jun 2019 10:38:41 +0800

Ah, so it was talking about range addresses all the time!
OK, I recommend say so instead, and hyperlinking
(info "(sed) Range Addresses") at each spot too. Thanks.

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

From: Assaf Gordon <assafgordon <at> gmail.com>
To: 積丹尼 Dan Jacobson <jidanni <at> jidanni.org>
Cc: 36202 <at> debbugs.gnu.org, Eric Blake <eblake <at> redhat.com>
Subject: Re: bug#36202: Add example of how to write the two addresses
Date: Sat, 29 Jun 2019 01:51:00 -0600

severity 36202 wishlist
stop

Hello,

On Fri, Jun 14, 2019 at 10:38:41AM +0800, 積丹尼 Dan Jacobson wrote:
> Ah, so it was talking about range addresses all the time!
> OK, I recommend say so instead, and hyperlinking
> (info "(sed) Range Addresses") at each spot too. Thanks.

I'm marking this as "wishlist", until someone gets around to improving
the manual (patches are always welcomed).

-assaf

Previous Next

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