From: Protesilaos Stavrou <info@protesilaos.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: "Basil L. Contovounesios" <contovob@tcd.ie>, emacs-devel@gnu.org
Subject: Re: modus-themes ELPA and etc/themes
Date: Sun, 21 Mar 2021 00:49:24 +0200 [thread overview]
Message-ID: <8735wpxwy3.fsf@protesilaos.com> (raw)
In-Reply-To: <874kh54in7.fsf@tcd.ie> (Basil L. Contovounesios's message of "Sat, 20 Mar 2021 21:31:08 +0000")
On 2021-03-20, 21:31 +0000, "Basil L. Contovounesios" <contovob@tcd.ie> wrote:
> Stefan Monnier <monnier@iro.umontreal.ca> writes:
>
>> OK, so it's a definite no for moving `etc/themes`.
>>
>> How 'bout moving just `modus-themes.el` (it's a fresh new file, so the
>> forensics aspect shouldn't matter that much, especially since the real
>> Git history is in the upstream repository rather than in emacs.git
>> anyway)? Part of the reason why `modus-themes.el` could be treated
>> differently is that it actually contains a fair bit of ELisp code, so it
>> would make sense to compile it.
>
> [Just for posterity - this was touched on in bug#45068 to an extent.]
A very short summary of that bug, as pertains to this point:
+ A file that resides in etc/themes cannot be loaded with just a
(require) call because it is not in the load-path.
+ We need such a functionality to load the main modus-themes.el from
within modus-{operandi,vivendi}-theme.el. The former contains the
bulk of the code, while the latter two expand the relevant parts into
actual themes.
+ To make everything work inside etc/themes we had to use the new
'require-theme' function, which accounts for that directory.
--
Protesilaos Stavrou
protesilaos.com
next prev parent reply other threads:[~2021-03-20 22:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-20 19:52 modus-themes ELPA and etc/themes Stefan Monnier
2021-03-20 20:23 ` Eli Zaretskii
2021-03-20 20:39 ` Stefan Monnier
2021-03-20 21:31 ` Basil L. Contovounesios
2021-03-20 22:49 ` Protesilaos Stavrou [this message]
2021-03-21 5:59 ` Eli Zaretskii
2021-03-26 21:41 ` Stefan Monnier
2021-03-27 6:05 ` Eli Zaretskii
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=8735wpxwy3.fsf@protesilaos.com \
--to=info@protesilaos.com \
--cc=contovob@tcd.ie \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).