texinfo-commits
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

branch master updated: * doc/texinfo.texi (@table): Edit and condense di


From: Gavin D. Smith
Subject: branch master updated: * doc/texinfo.texi (@table): Edit and condense discussion of blank lines.
Date: Mon, 17 Oct 2022 17:17:39 -0400

This is an automated email from the git hooks/post-receive script.

gavin pushed a commit to branch master
in repository texinfo.

The following commit(s) were added to refs/heads/master by this push:
     new 48fbb9c402 * doc/texinfo.texi (@table): Edit and condense discussion 
of blank lines.
48fbb9c402 is described below

commit 48fbb9c402e411af98a98700457704cfdd6a33cb
Author: Gavin Smith <gavinsmith0123@gmail.com>
AuthorDate: Mon Oct 17 22:17:30 2022 +0100

    * doc/texinfo.texi (@table): Edit and condense discussion
    of blank lines.
---
 ChangeLog        |  5 +++++
 doc/texinfo.texi | 16 +++++++++-------
 2 files changed, 14 insertions(+), 7 deletions(-)

diff --git a/ChangeLog b/ChangeLog
index ef45e15bb6..0122b82368 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,8 @@
+2022-10-17  Gavin Smith  <gavinsmith0123@gmail.com>
+
+       * doc/texinfo.texi (@table): Edit and condense discussion
+       of blank lines.
+
 2022-10-17  Gavin Smith  <gavinsmith0123@gmail.com>
 
        * doc/texinfo.texi (@minus): Remove duplicate text about
diff --git a/doc/texinfo.texi b/doc/texinfo.texi
index 408323d319..314b1dba8c 100644
--- a/doc/texinfo.texi
+++ b/doc/texinfo.texi
@@ -7579,13 +7579,15 @@ paragraphs.  But only the text on the same line as the 
@code{@@item}
 will be placed in the first column (including any footnotes).
 You do not need to type anything for an empty second column.
 
-Normally, you should put a blank line before an @code{@@item} line
-(except the first one).  Except when the entries are very brief, a
-blank line looks better in some output formats.
-End the table with a line consisting of @code{@@end table}.  Some output
-formats automatically start a new paragraph after the table, so
-it is in general better to follow the end of the table by a blank line,
-to obtain analogous output for other output formats.
+Normally, you should put a blank line between table entries.  This puts
+a blank line in the Info file, which looks better unless the entries
+are very brief.
+
+End the table with a line consisting of @code{@@end table}.
+Follow the end of the table by a blank line for consistent formatting
+across output formats.
+
+@c TeX aloways starts a new paragraph after the table
 
 @need 1500
 For example, the following table highlights the text in the first



reply via email to

[Prev in Thread] Current Thread [Next in Thread]