GNU bug report logs - #45068
[PATCH] 28.0.50; Update Modus themes 1.0.2 (backward-incompatible)

Previous Next

Full log

Message #41 received at 45068 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Stefan Kangas <stefankangas <at> gmail.com>
Cc: contovob <at> tcd.ie, info <at> protesilaos.com, 45068 <at> debbugs.gnu.org,
 juri <at> linkov.net
Subject: Re: bug#45068: [PATCH] 28.0.50;
 Update Modus themes 1.0.2 (backward-incompatible)
Date: Fri, 11 Dec 2020 16:32:42 +0200

> From: Stefan Kangas <stefankangas <at> gmail.com>
> Date: Fri, 11 Dec 2020 08:16:47 -0600
> Cc: juri <at> linkov.net, info <at> protesilaos.com, contovob <at> tcd.ie, 
> 	45068 <at> debbugs.gnu.org
> 
> Right.  Well, I don't exactly have a strong opinion either way.  But I
> do think that we should be consistent: it would be confusing to have
> some themes in "etc/themes" and some in "lisp/themes".

Why not have all of them in etc/themes?

> If we can't move all themes to "lisp/themes" and we don't want to use
> "lisp/themes" just for support files, to my mind the only remaining way
> forward is to add some way to byte-compile (perhaps only some?) files in
> "etc/themes".

What theme-related files need to be byte-compiled, and why?

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.