From: Eli Zaretskii <eliz@gnu.org>
To: Mauro Aranda <maurooaranda@gmail.com>,
Stefan Kangas <stefankangas@gmail.com>
Cc: thievol@posteo.net, 65468@debbugs.gnu.org
Subject: bug#65468: 29.1; describe-theme fails to describe some themes not loaded
Date: Sat, 09 Sep 2023 14:47:33 +0300 [thread overview]
Message-ID: <835y4jva96.fsf@gnu.org> (raw)
In-Reply-To: <a13a7651-c382-9923-a9b5-6b8c2e291a89@gmail.com> (message from Mauro Aranda on Sat, 9 Sep 2023 08:33:27 -0300)
> Date: Sat, 9 Sep 2023 08:33:27 -0300
> Cc: 65468@debbugs.gnu.org
> From: Mauro Aranda <maurooaranda@gmail.com>
>
> On 26/8/23 04:57, Eli Zaretskii wrote:
> >> From: Thierry Volpiatto <thievol@posteo.net>
> >> Cc: 65468@debbugs.gnu.org
> >> Date: Wed, 23 Aug 2023 13:12:28 +0000
> >>
> >>> If so, I think this should go to master, not to the emacs-29 branch.
> >>
> >> I will not push anything, just proposing patch if any interest to fix
> >> this issue, here a new patch that provide a separate function for this
> >> part of code:
> >
> > Thanks, installed on master (after fixing a small blunder).
> >
>
> It seems to me that there's nothing left to do here. The patch by
> Thierry got installed, I fixed the leuven themes and Prot reported that
> he fixed the modus-themes on his end.
>
> Can we close it? Or did I miss something?
Fine by me. Stefan?
next prev parent reply other threads:[~2023-09-09 11:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-23 8:44 bug#65468: 29.1; describe-theme fails to describe some themes not loaded Thierry Volpiatto
2023-08-23 9:53 ` Mauro Aranda
2023-08-23 11:01 ` Thierry Volpiatto
2023-08-23 11:57 ` Eli Zaretskii
2023-08-24 10:16 ` Mauro Aranda
2023-08-25 3:48 ` Protesilaos Stavrou
2023-08-23 11:47 ` Eli Zaretskii
2023-08-23 13:12 ` Thierry Volpiatto
2023-08-26 7:57 ` Eli Zaretskii
2023-08-26 15:31 ` Thierry Volpiatto
2023-09-09 11:33 ` Mauro Aranda
2023-09-09 11:47 ` Eli Zaretskii [this message]
2023-09-09 11:51 ` 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
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=835y4jva96.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=65468@debbugs.gnu.org \
--cc=maurooaranda@gmail.com \
--cc=stefankangas@gmail.com \
--cc=thievol@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).