> Date: Wed, 23 Sep 2026 21:19:09 +0200 > From: Patrice Dumas <[email protected]> > > > > As a side note, having an (unused) @setfilename consistent with the output > > > directory for emacs manuals is told in a comment in doc/emacs/Makefile.in: > > > ## Where the output files go. > > > ## Note that the setfilename command in the .texi files assumes this. > > > I would still suggest using a simpler @setfilename, like > > > @setfilename emacs-xtra.info > > > in the emacs manuals, mainly for clarity. > > > > Sorry, I can't follow what you are proposing here. What makes the > > @setfilename > > unused, for example? > > It is something for the emacs developers, the already use -o, so they > could set @setfilename to the base file name, which is more expected > than what they do.
How do you expect us to do that, when we want to support a wide range of Texinfo versions with the same Texinfo sources and Makefile's? And why impose such a task on use in the first place? There's nothing particularly wrong with the current behavior, even if it looks surprising at first sight: it is deterministic and easily explained. And it has been with us for a long enough time.
