Re: rethinking @def*

[Eli Zaretskii]

> From: Gavin Smith <gavinsmith0123@gmail.com>
> Date: Tue, 26 Jul 2022 20:30:16 +0100
> Cc: wl@gnu.org, pertusus@free.fr, bug-texinfo@gnu.org
> 
> On Tue, Jul 26, 2022 at 09:53:04PM +0300, Eli Zaretskii wrote:
> > > From: Gavin Smith <gavinsmith0123@gmail.com>
> > > Date: Tue, 26 Jul 2022 19:40:32 +0100
> > > Cc: pertusus@free.fr, bug-texinfo@gnu.org
> > > 
> > > > Yes, and I consider this as bad.  As I mentioned in my previous
> > > > e-mail, such a change would ruin any fine-tuning of the formatting – a
> > > > formatting that stayed unmodified for a very long time.
> > > 
> > > We could see what the change would do to various documents once it is
> > > implemented.
> > 
> > How would you see that?  Most documents won't see this version before
> > it is released, usually years after it's released, because
> > introduction of new package versions into distros is slow.  Most
> > complaints won't show up until many noons after Texinfo with these
> > changes hits the streets.
> 
> I meant by downloading and building some manuals from the Internet to
> find where the problematic cases might occur.

Sure.  But what would be the chances of hitting the important examples
by trying random manuals?