From: Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: yantar92@posteo.net, 74844@debbugs.gnu.org,
Suhail Singh <suhailsingh247@gmail.com>
Subject: bug#74844: 29.4; m-buffer: Broken Top Directory node in Info manual due to malformed Texinfo direntry
Date: Sun, 15 Dec 2024 17:23:16 -0500 [thread overview]
Message-ID: <jwvh674si4j.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <86frmorejn.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 15 Dec 2024 20:23:24 +0200")
>> > Why do you suggest removing TEXINFO_DIR_TITLE
>> Because of this comment in ox-texinfo.el which suggests that it is
>> obsolete:
> FWIW, I disagree with that decision of Org folks.
It's obsolete because it was renamed to TEXINFO_DIR_NAME because I don't
think it's right to think of it as a "title".
> That there is a default does not mean that we need to discard the
> description when we do have it. Discarding it loses important
> information (which programs like install-info use).
It could lose important information, in which case we wouldn't want to
discard it. But here it just duplicates the default.
> This is a wrong interpretation. FILENAME here is the Info file name,
> not the Texinfo file name (the latter is the file name of the Texinfo
> source).
The Info file name is derived from the Texinfo filename.
Stefan
next prev parent reply other threads:[~2024-12-15 22:23 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-13 1:31 bug#74844: 29.4; m-buffer: Broken Top Directory node in Info manual due to malformed Texinfo direntry Suhail Singh
2024-12-13 21:50 ` bug#74844: " Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-14 8:08 ` Eli Zaretskii
2024-12-14 13:53 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-14 14:47 ` Eli Zaretskii
2024-12-14 21:05 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-15 6:19 ` Eli Zaretskii
2024-12-15 13:38 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-15 14:00 ` Eli Zaretskii
2024-12-15 22:08 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-14 21:48 ` bug#74844: 29.4; " Suhail Singh
2024-12-15 7:17 ` Eli Zaretskii
2024-12-15 17:53 ` Suhail Singh
2024-12-15 18:23 ` Eli Zaretskii
2024-12-15 18:46 ` Suhail Singh
2024-12-15 22:23 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2024-12-15 22:20 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-15 23:25 ` Suhail Singh
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=jwvh674si4j.fsf-monnier+emacs@gnu.org \
--to=bug-gnu-emacs@gnu.org \
--cc=74844@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=suhailsingh247@gmail.com \
--cc=yantar92@posteo.net \
/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).