From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: 75123@debbugs.gnu.org
Subject: bug#75123: [PATCH] Set makeinfo-run-command to texi2any when possible
Date: Fri, 27 Dec 2024 09:16:59 +0200 [thread overview]
Message-ID: <86ed1ty4r8.fsf@gnu.org> (raw)
In-Reply-To: <CADwFkmnW2miRHR57jzi7pkVUzNX5-qY_nakS0d8+wxTWKxYhVQ@mail.gmail.com> (message from Stefan Kangas on Thu, 26 Dec 2024 20:12:54 +0000)
> From: Stefan Kangas <stefankangas@gmail.com>
> Date: Thu, 26 Dec 2024 20:12:54 +0000
>
> Please see the attached patch, intended for master.
>
> From 9563aeabb5d48893c5e1054dd0c1172d20c0bed2 Mon Sep 17 00:00:00 2001
> From: Stefan Kangas <stefankangas@gmail.com>
> Date: Thu, 26 Dec 2024 21:06:29 +0100
> Subject: [PATCH] Set makeinfo-run-command to texi2any when possible
>
> In recent Texinfo, "makinfo" is an alias for "texi2any". Make
> `makeinfo-run-command` heed this request in the texinfo documentation:
>
> "Going forward, we ask authors of Texinfo documents to use only
> texi2any."
>
> See (info "(texinfo) History").
Sorry, I'm against this change. People still have old versions of
Texinfo installed, including those where texi2any was not even
present. I understand what the Texinfo developers say as advice to
people who install latest version of Texinfo, not as a general rule to
other programs which invoke makeinfo.
In practice, in latest versions, 'makeinfo' is just a copy (or even a
symlink) to texi2any. So we gain absolutely nothing by this change,
while the disadvantages for users who have old versions of makeinfo
are clear and present.
So let's not make this change.
next prev parent reply other threads:[~2024-12-27 7:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-26 20:12 bug#75123: [PATCH] Set makeinfo-run-command to texi2any when possible Stefan Kangas
2024-12-27 7:16 ` Eli Zaretskii [this message]
2024-12-27 12:55 ` Eli Zaretskii
2024-12-27 14:05 ` Stefan Kangas
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86ed1ty4r8.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=75123@debbugs.gnu.org \
--cc=stefankangas@gmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.