From: Eli Zaretskii <eliz@gnu.org>
To: Mats Lidell <matsl@gnu.org>
Cc: 74042@debbugs.gnu.org
Subject: bug#74042: [PATCH] Accept texi2any for version identification
Date: Mon, 28 Oct 2024 05:23:48 +0200 [thread overview]
Message-ID: <86r0807vwb.fsf@gnu.org> (raw)
In-Reply-To: <87h68x44e0.fsf@gnu.org> (message from Mats Lidell on Sun, 27 Oct 2024 22:33:59 +0100)
> From: Mats Lidell <matsl@gnu.org>
> Cc: 74042@debbugs.gnu.org
> Date: Sun, 27 Oct 2024 22:33:59 +0100
>
> > Eli Zaretskii writes:
> > Why would users do that by invoking texi2any directly?
>
> Because texi2any is a tool for generating info files from texi files!?
>
> We started to use it with GNU Hyperbole and got into this subtle issue (and
> wasted some hours due to it.)
IMNSHO, as someone who is involved in the Texinfo development for many
years, the GNU Hyperbole made a mistake by doing so.
> > FTR, I'm very unhappy about this change. I don't think we should support
> > this. It is not future-proof.
>
> Well to take a step back. Is not the root problem here that the version number
> of a tool is used for checking whether certain feature is supported in the
> info file? If the check would be more direct then the tool would not matter as
> long as the info file is correct!?
Texinfo doesn't let us check for features, sadly. The only way to
know which features are present is by looking at the version.
next prev parent reply other threads:[~2024-10-28 3:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-27 8:35 bug#74042: [PATCH] Accept texi2any for version identification Mats Lidell
2024-10-27 9:20 ` Eli Zaretskii
2024-10-27 17:50 ` Mats Lidell
2024-10-27 19:18 ` Eli Zaretskii
2024-10-27 21:01 ` Stefan Kangas
2024-10-27 21:33 ` Mats Lidell
2024-10-28 3:23 ` Eli Zaretskii [this message]
2024-10-27 9:47 ` Stefan Kangas
2024-10-27 10:11 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86r0807vwb.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=74042@debbugs.gnu.org \
--cc=matsl@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).