[Top][All Lists]

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

Re: texinfo-6.8.90 pretest

From: Patrice Dumas
Subject: Re: texinfo-6.8.90 pretest
Date: Thu, 20 Oct 2022 16:42:45 +0200

On Thu, Oct 20, 2022 at 01:20:19PM +0200, Robert Pluim wrote:
> >>>>> On Wed, 19 Oct 2022 17:01:34 +0100, Gavin Smith 
> >>>>> <gavinsmith0123@gmail.com> said:
>     Gavin> The first pretest for the Texinfo 7.0 release has been uploaded to
>     Gavin> https://alpha.gnu.org/gnu/texinfo/texinfo-6.8.90.tar.xz
>     Gavin> There have been many changes since the previous release (see 
> below),
>     Gavin> but among the most notable are the addition of LaTeX and EPUB 3 as
>     Gavin> texi2any output formats.
> Building the latest emacs master manuals with the latest texinfo
> master gives the following warning which I donʼt see with texinfo 6.7:
>     killing.texi:573: warning: @pxref should not appear in @w
> The relevant source looks like this:
>     platforms, Emacs can yank these objects with the @code{yank-media}
>     command---but only in modes that have support for it (@w{@pxref{Yanking
>     Media,,, elisp, The Emacs Lisp Reference Manual}}).
> Is there a reason for this new warning?

Previously there were no check at all on @w content.  I assumed that @w
could only contain "simple text" which meant all the inline @-commands
except for 'titlefont', 'anchor', 'footnote', 'verb', 'xref', 'ref',
'pxref', 'inforef'.

Actually, for this specific example it seems to me that the code put on
@w is too long to allow for correct display.  I checked in HTML, and
indeed, the non breakable part seems to me to be too long to allow for
good rendering, unless the browser width is within a specific range.
Wouldn't you obtain the effect you want or even something better by
simply using @w for the arguments of the @pxref instead, possible adding
a third argument in @w?

It could also be possible to accept more commands in @w without giving a


reply via email to

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