From: Stephen Berman <stephen.berman@gmx.net>
To: Philip Kaludercic <philipk@posteo.net>
Cc: Protesilaos Stavrou <info@protesilaos.com>, 64548@debbugs.gnu.org
Subject: bug#64548: 29.0.92; Modus Themes Info manual is in "Unknown category"
Date: Mon, 10 Jul 2023 22:09:30 +0200 [thread overview]
Message-ID: <87wmz7fs05.fsf@gmx.net> (raw)
In-Reply-To: <87h6qbkgf5.fsf@posteo.net> (Philip Kaludercic's message of "Mon, 10 Jul 2023 14:08:30 +0000")
On Mon, 10 Jul 2023 14:08:30 +0000 Philip Kaludercic <philipk@posteo.net> wrote:
> I've added Protesilaos to the CCs, in case he hasn't seen the bug
> report. (Generally it is recommended to add a "X-Debbugs-CC" header if
> you can find the maintainer).
>
> Stephen Berman <stephen.berman@gmx.net> writes:
>
>> On Sun, 09 Jul 2023 22:21:55 +0200 Stephen Berman <stephen.berman@gmx.net> wrote:
>>
>>> After building Emacs from the release branch or from master, the
>>> info/dir file looks like this (excerpted):
>>>
>>> [...]
>>> Unknown category
>>> * Modus Themes: (modus-themes). Elegant, highly legible and customizable
>>> themes.
>>>
>>>
>>> The two odds things about the last entry are its category and the extra
>>> space after the asterisk.
>>> [...]
>>
>> I bisected the problem to the following commit:
>>
>> 8a9839348fb8762c8843362595f2ca9de60d515c is the first bad commit
>> commit 8a9839348fb8762c8843362595f2ca9de60d515c
>> Author: Protesilaos Stavrou <info@protesilaos.com>
>> Date: Wed Aug 3 14:32:38 2022 +0300
>>
>> Update modus-themes to their version 2.5.0
>>
>> And the problem is due, to my surprise, to whitespace in the Org markup
>> at the beginning of modus-themes.org. This suggests to me a problem
>> somewhere in org/ox-texinfo.el,
>
> Why do you think this is a problem with exporting, rather than with
> parsing?
I wasn't thinking of any specific cause, I just saw that ox-texinfo.el
is used in the Makefile, but I know nothing about it.
> Either way, it might be worth involving some Org people in
> this report.
Yes, that I did mean to suggest.
>> but I'm not familiar with that code, so
>> I'll leave pursuing it to someone who is. In the meantime, building
>> with the attached patch against current emacs-29 restores the correct
>> dir file.
[...]
On Mon, 10 Jul 2023 22:49:20 +0300 Protesilaos Stavrou <info@protesilaos.com> wrote:
>> From: Philip Kaludercic <philipk@posteo.net>
>> Date: Mon, 10 Jul 2023 14:08:30 +0000
>>
>> I've added Protesilaos to the CCs, in case he hasn't seen the bug
>> report. (Generally it is recommended to add a "X-Debbugs-CC" header if
>> you can find the maintainer).
>
> Thank you Philip, Stephen!
>
> Stephen, I am fine with the patch. I was not expecting the spaces to
> create such a problem.
Thanks. I do hope an Org developer familiar with the generation of
.texi files from .org sources will chime in, and in any case it's up to
Eli to decide whether the patch should be installed.
Steve Berman
prev parent reply other threads:[~2023-07-10 20:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-09 20:21 bug#64548: 29.0.92; Modus Themes Info manual is in "Unknown category" Stephen Berman
2023-07-10 10:20 ` Stephen Berman
2023-07-10 14:08 ` Philip Kaludercic
2023-07-10 19:49 ` Protesilaos Stavrou
2023-07-11 11:11 ` Eli Zaretskii
2023-07-10 20:09 ` Stephen Berman [this message]
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=87wmz7fs05.fsf@gmx.net \
--to=stephen.berman@gmx.net \
--cc=64548@debbugs.gnu.org \
--cc=info@protesilaos.com \
--cc=philipk@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).