[no subject]

[Gavin D. Smith]

branch: master
commit e97bc6fbac3a38fe42310c3a37941fcce40405e3
Author: Gavin Smith <gavinsmith0123@gmail.com>
AuthorDate: Mon Dec 30 01:25:41 2024 +0000

    Remove \bfafterword for def formatting
    
    * doc/texinfo.tex (\bfafterword): Remove.  This made the
    second word in parentheses bold on a definition line, but
    only after an &keyword.  So in "@defun func &word (foo bar)",
    "bar" would be printed in bold.
    
    I do not know the purpose of this but it is presumably something
    to do with Emacs Lisp syntax.  But in some cases in the Emacs Lisp
    manual this font style appeared inappropriate, for example in
    
    @defmac cl-defmethod name [qualifier] arguments [&context (expr 
spec)@dots{}] &rest [docstring] body
    
    the word "spec" was in bold, and nothing else.  As no attempt is
    made to do anything like this in texi2any and it is likely not
    appropriate in many cases, we are better getting rid of the feature.
---
 ChangeLog       | 19 +++++++++++++++++++
 doc/texinfo.tex |  6 ++----
 2 files changed, 21 insertions(+), 4 deletions(-)

diff --git a/ChangeLog b/ChangeLog
index d28fc49a03..203f4ff5cc 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,22 @@
+2024-12-30  Gavin Smith <gavinsmith0123@gmail.com>
+
+       Remove \bfafterword for def formatting
+
+       * doc/texinfo.tex (\bfafterword): Remove.  This made the
+       second word in parentheses bold on a definition line, but
+       only after an &keyword.  So in "@defun func &word (foo bar)",
+       "bar" would be printed in bold.
+       
+       I do not know the purpose of this but it is presumably something
+       to do with Emacs Lisp syntax.  But in some cases in the Emacs Lisp
+       manual this font style appeared inappropriate, for example in
+       
+       @defmac cl-defmethod name [qualifier] arguments [&context (expr 
spec)@dots{}] &rest [docstring] body
+       
+       the word "spec" was in bold, and nothing else.  As no attempt is
+       made to do anything like this in texi2any and it is likely not
+       appropriate in many cases, we are better getting rid of the feature.
+
 2024-12-30  Gavin Smith <gavinsmith0123@gmail.com>
 
        * doc/texinfo.tex (\boldbrax, \parenbrackglpyhs):
diff --git a/doc/texinfo.tex b/doc/texinfo.tex
index 1802f64f5b..22dc4d1545 100644
--- a/doc/texinfo.tex
+++ b/doc/texinfo.tex
@@ -3,7 +3,7 @@
 % Load plain if necessary, i.e., if running under initex.
 \expandafter\ifx\csname fmtname\endcsname\relax\input plain\fi
 %
-\def\texinfoversion{2024-12-29.23}
+\def\texinfoversion{2024-12-30.00}
 %
 % Copyright 1985, 1986, 1988, 1990-2024 Free Software Foundation, Inc.
 %
@@ -7965,7 +7965,7 @@ might help (with 'rm \jobname.?? \jobname.??s')%
   }
   \globaldefs=1 \defcharsdefault
 
-  \gdef\parenbrackglyphs{\let(=\opnr\let)=\clnr\let[=\lbrb\let]=\rbrb}
+  \gdef\parenbrackglyphs{\let(=\opnr\let)=\cpnr\let[=\lbrb\let]=\rbrb}
   \gdef\magicamp{\let&=\amprm}
 }
 \let\ampchar\&
@@ -7994,13 +7994,11 @@ might help (with 'rm \jobname.?? \jobname.??s')%
     \fi
   \fi
 }
-\def\bfafterword#1 {#1 \bf}
 
 % opening and closing parentheses in roman font
 \def\opnr{%
   \global\advance\parencount by 1
   {\parenfont(}%
-  \infirstlevel \bfafterword
 }
 \def\cpnr{%
   {\parenfont)}%