GNU bug report logs - #21845
sed docs bug: No documentation of which commands must be terminated by newlines

Previous Next

Full log

View this message in rfc822 format

From: Jim Meyering <jim <at> meyering.net>
To: Assaf Gordon <assafgordon <at> gmail.com>
Cc: Ori Avtalion <ori <at> avtalion.name>, 21845 <at> debbugs.gnu.org
Subject: bug#21845: sed docs bug: No documentation of which commands must be terminated by newlines
Date: Tue, 24 Jan 2017 20:34:37 -0800

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

On Tue, Jan 24, 2017 at 7:51 PM, Assaf Gordon <assafgordon <at> gmail.com> wrote:
> Hello Ori,
>
> Sorry for the delayed response.
>
> On Fri, Nov 06, 2015 at 05:44:04PM +0200, Ori Avtalion wrote:
>>
>> Some commands, due to their syntax, cannot be followed by semicolons
>> [...]
>> I can find no mention of which commands this applies to.
>> This limitation should be mentioned next to each such command.
>
>
> Thank you for mentioning this. Indeed an important piece of information.
>
> I'm considering adding a new section about this.
> Draft attached, comments welcomed.

Thank you for that addition.
I did a quick once-over and suggest these changes:

[sed-0001-doc-new-multiple-commands-syntax-section-touch-up.patch (text/x-patch, attachment)]

Previous Next

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