unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Philip Kaludercic <philipk@posteo.net>
To: Tor Kringeland <tor.a.s.kringeland@ntnu.no>
Cc: help-gnu-emacs@gnu.org, public@protesilaos.com
Subject: Re: Using built-in modus themes
Date: Fri, 04 Mar 2022 08:29:55 +0000	[thread overview]
Message-ID: <87fsnyunlo.fsf@posteo.net> (raw)
In-Reply-To: <m2r17iud5z.fsf@ntnu.no> (Tor Kringeland's message of "Thu, 03 Mar 2022 19:03:04 +0100")

Tor Kringeland <tor.a.s.kringeland@ntnu.no> writes:

> I'm trying to configure and use the modus themes as described in [1].
> I'm on a build of Emacs 29 so these are built in.  While I can enable
> the themes by using `load-theme', if I execute
>
>   (require 'modus-themes)
>
> as described in [1] I get an error saying that the file is missing.
> However if I first load a theme using `load-theme', then executing the
> above yields no error.
>
> Shouldn't running the above work since the themes are part of Emacs now
> (so that I could put it in my config)?  I'm running `emacs -Q' and this
> fails then.

I agree, it should, an I have also had issues with this problem.

From what I see, the "issue" is that modus-themes is not in the
`load-path'.  When you `load-theme' one of the two modus-themes,
`modus-themes' is also added to `features', the list maintaining
activated features.  `require' checks this list before loading a
feature, and as it has already been added, no error is thrown and it
appears to work.

One way this could be solved would be to add the themes directory to
`load-path', but I suspect there is some reason this hasn't been done
already.

(I have CC'ed Protesilaos to see what he has to say).

-- 
	Philip Kaludercic



  reply	other threads:[~2022-03-04  8:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-03 18:03 Using built-in modus themes Tor Kringeland
2022-03-04  8:29 ` Philip Kaludercic [this message]
2022-03-04  8:56   ` Protesilaos Stavrou
2022-03-04 16:15     ` Christopher Dimech
2022-03-04 16:39     ` Tor Kringeland

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=87fsnyunlo.fsf@posteo.net \
    --to=philipk@posteo.net \
    --cc=help-gnu-emacs@gnu.org \
    --cc=public@protesilaos.com \
    --cc=tor.a.s.kringeland@ntnu.no \
    /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.
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).