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

Previous Next

Full log

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

From: Assaf Gordon <assafgordon <at> gmail.com>
To: Ori Avtalion <ori <at> avtalion.name>
Cc: 21845 <at> debbugs.gnu.org
Subject: Re: bug#21845: sed docs bug: No documentation of which commands must
 be terminated by newlines
Date: Wed, 25 Jan 2017 03:51:51 +0000

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

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.

>The documentation uses 'file-name' instead of 'filename'.

Fixed as well.

regards,
- assaf

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

Previous Next

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