|
From: | Assaf Gordon |
Subject: | bug#21845: sed docs bug: No documentation of which commands must be terminated by newlines |
Date: | Fri, 27 Jan 2017 02:54:12 +0000 |
User-agent: | Mutt/1.5.23 (2014-03-12) |
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 <address@hidden> wrote:On Fri, Nov 06, 2015 at 05:44:04PM +0200, Ori Avtalion wrote:Some commands, due to their syntax, cannot be followed by semicolonsThank 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
Description: Text Data
[Prev in Thread] | Current Thread | [Next in Thread] |