> From: Robert Pluim <[email protected]> > Cc: Gavin Smith <[email protected]>, Texinfo <[email protected]>, > Eli Zaretskii <[email protected]> > Date: Thu, 20 Oct 2022 18:22:03 +0200 > > >>>>> On Thu, 20 Oct 2022 17:47:43 +0200, Patrice Dumas <[email protected]> > >>>>> 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?
