this post was submitted on 29 Nov 2023
1 points (100.0% liked)

Emacs

311 readers
1 users here now

A community for the timeless and infinitely powerful editor. Want to see what Emacs is capable of?!

Get Emacs

Rules

  1. Posts should be emacs related
  2. Be kind please
  3. Yes, we already know: Google results for "emacs" and "vi" link to each other. We good.

Emacs Resources

Emacs Tutorials

Useful Emacs configuration files and distributions

Quick pain-saver tip

founded 1 year ago
MODERATORS
rglullis@communick.news
raphael@communick.news
1
"Loading a theme can run Lisp code" - wtf (alien.top)
submitted 11 months ago by ghiste@alien.top to c/emacs@communick.news
2 comments fedilink hide all child comments
 

Hi,

every time I try to get into orgmode (which is great) I have to deal with emacs (I ususally use nvim) and I feel that regardless of any productivity boost orgmode may give me, I will never recover the time I have wasted with emacs configuration issues - it seems to be just a very, very fragile ecosystem...

Here is the latest problem:

I want to use the modus-operandi theme and have added a use-package clause copied from the documentation.

But now when I open emacs I get a prompt, informing me that loading a theme can run lisp code and if I wanted to proceed, I say yes, I am asked if this theme should be deemed safe for future sessions, I say yes and then the theme loads fine - but only for this sesssion.

When I close emacs the whole thing starts again, so my question is: How can I get rid of this annoying prompt?

top 2 comments
sorted by: hot top controversial new old
[–] noooit@alien.top 1 points 11 months ago (1 children)

It's a weird default. The file is literally a elisp code with .el like almost everything else.

[–] scribe36@alien.top 1 points 11 months ago

No—it’s not. These days we think we need code for everything. Emacs is from times when people didn’t default to that assumption. Someone may have loaded a theme thinking it will just load some style sheet and not run code. Then—be surprised that loading a “theme” meant running code.