[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[groff] 18/23: doc/groff.texi.in: Recast `output`/`\!` advice.
From: |
G. Branden Robinson |
Subject: |
[groff] 18/23: doc/groff.texi.in: Recast `output`/`\!` advice. |
Date: |
Wed, 16 Oct 2024 15:00:30 -0400 (EDT) |
gbranden pushed a commit to branch master
in repository groff.
commit da01b95bed31f7c341b93e13f91aa361745e17d0
Author: G. Branden Robinson <g.branden.robinson@gmail.com>
AuthorDate: Tue Oct 15 11:15:23 2024 -0500
doc/groff.texi.in: Recast `output`/`\!` advice.
---
doc/groff.texi.in | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/doc/groff.texi.in b/doc/groff.texi.in
index df7ae39ea..1564c732d 100644
--- a/doc/groff.texi.in
+++ b/doc/groff.texi.in
@@ -15760,10 +15760,10 @@ which is read to the end of the input line in copy
mode.
@strong{Caution:@:} Use of these features can put syntactically invalid
content into GNU @command{troff}'s output, which @code{groff}'s output
-drivers then fail to process. They are normally needed only for
-instructions to a postprocessor that does something with the output
-before sending it to the output device, filtering out @var{contents}
-again.
+drivers then fail to process. @code{output} and use of @code{\!} from
+the top-level diversion are normally needed only for instructions to a
+postprocessor that does something with the output before sending it to
+the output device, filtering out @var{contents} again.
@c TODO: Once the dust settles from Savannah #63074, document how these
@c can be used to construct device extension commands without special
@c character processing.
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [groff] 18/23: doc/groff.texi.in: Recast `output`/`\!` advice.,
G. Branden Robinson <=