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

Previous Next

Full log

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

From: Assaf Gordon <assafgordon <at> gmail.com>
To: Jim Meyering <jim <at> meyering.net>
Cc: Ori Avtalion <ori <at> avtalion.name>, 21845 <at> debbugs.gnu.org
Subject: Re: bug#21845: sed docs bug: No documentation of which commands must
 be terminated by newlines
Date: Fri, 27 Jan 2017 02:54:12 +0000

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

Hello Jim,

On Tue, Jan 24, 2017 at 08:34:37PM -0800, Jim Meyering wrote:
>On Tue, Jan 24, 2017 at 7:51 PM, Assaf Gordon <assafgordon <at> gmail.com> wrote:
>> On Fri, Nov 06, 2015 at 05:44:04PM +0200, Ori Avtalion wrote:
>>>
>>> Some commands, due to their syntax, cannot be followed by semicolons
>>
>> Thank you for mentioning this. Indeed an important piece of information.
>>
>> I'm considering adding a new section about this.
>
> I did a quick once-over and suggest these changes:

Thanks for the review.
I've incorporated your changes, but also added two small items
(about 'e' and 's///[ew]') - so sending again before pushing anything.

comments again welcomed,
- 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.