[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[PATCH] doc: list all commands that have to be terminated by a newline
From: |
Arkadiusz Drabczyk |
Subject: |
[PATCH] doc: list all commands that have to be terminated by a newline |
Date: |
Tue, 4 Feb 2025 20:41:29 +0100 |
Signed-off-by: Arkadiusz Drabczyk <arkadiusz@drabczyk.org>
---
doc/sed.texi | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/doc/sed.texi b/doc/sed.texi
index c1b2c84..f70543c 100644
--- a/doc/sed.texi
+++ b/doc/sed.texi
@@ -634,9 +634,10 @@ sed -e '/^foo/d' -f script2.sed input.txt > output.txt
@cindex @command{a}, and semicolons
@cindex @command{c}, and semicolons
@cindex @command{i}, and semicolons
-Commands @command{a}, @command{c}, @command{i}, due to their syntax,
-cannot be followed by semicolons working as command separators and
-thus should be terminated
+Commands @command{a}, @command{c}, @command{e}, @command{i},
+@command{r}, @command{R}, @command{w}, @command{W}, due to their
+syntax, cannot be followed by semicolons working as command separators
+and thus should be terminated
with newlines or be placed at the end of a @var{script} or @var{script-file}.
Commands can also be preceded with optional non-significant
whitespace characters.
--
2.45.2