[Top][All Lists]

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

Re: texinfo-6.8.90 pretest

From: Eli Zaretskii
Subject: Re: texinfo-6.8.90 pretest
Date: Thu, 20 Oct 2022 19:36:42 +0300

> From: Robert Pluim <rpluim@gmail.com>
> Cc: Gavin Smith <GavinSmith0123@gmail.com>,  Texinfo <bug-texinfo@gnu.org>,
>     Eli Zaretskii <eliz@gnu.org>
> Date: Thu, 20 Oct 2022 18:22:03 +0200
> >>>>> On Thu, 20 Oct 2022 17:47:43 +0200, Patrice Dumas <pertusus@free.fr> 
> >>>>> said:
>     Gavin> On Thu, Oct 20, 2022 at 01:20:19PM +0200, Robert Pluim wrote:
>     >> >> 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?
>     >> 
>     Gavin> I don't see any problem with putting @pxref inside @w.  In my 
> opinion
>     Gavin> it should be fine to put any Texinfo commands that occur inside
>     Gavin> paragraphs inside @w.  This was a very recent change (2022-10-02).
>     Patrice> I imagined that @*ref in @w could only be mistake, as would also 
> be
>     Patrice> 'titlefont', 'anchor', 'footnote', 'verb', 'xref', 'ref', 
> 'pxref',
>     Patrice> 'inforef'.
>     Patrice> I can change such as to have @w contain anything that can happen 
> in a
>     Patrice> paragraph.
> I think that would be good. Eli has good taste in this sort of
> stuff. Eli?

I was surprised to hear that @w is used around a cross-reference.  I
admit I still don't understand the need: AFAIK all the viewers for all
the output formats can cope with a reference that is broken between
two lines?  So what exactly is the rationale for this usage?

reply via email to

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