Teemu Likonen <[email protected]> writes:
> [1:text/plain Hide]
>
> * 2026-03-18 11:59:22-0400, [email protected] wrote:
>
>> Have you considered deleting the faces (turn off the check mark) that
>> have the Lisp expressions, saving your theme, load theme again, and
>> adding the deleted faces by clicking on ‘Insert Additional Face’ (near
>> the end of the *Custom Theme* buffer)?
>
> The end result is the same Lisp expression in the theme file. Property
> list's elements in the face settings are sometimes in different order
> but that shouldn't matter because property lists are accessed in
> key-value basis.
>
> After your suggested operations the theme editor shows face settings in
> friendly customize format _once_ but later it always shows them as Lisp
> expressions. After all it's the same expression and it's not useful to
> change that. The bug or configuration is somewhere outside the theme
> file.
Unfortunately, themes are complex and customize is complex,
and this combines both. It appears to be an error that
should be reported (M-x report-emacs-bug).
1. If we start with (info "(emacs) Creating Custom Themes")
and create a new theme, the manual says:
"After specifying the Custom theme's faces and variables, type ‘C-x
C-s’ (‘custom-theme-write’)..."
When that is checked using C-h c, then C-x C-s has that
binding. But if you change the empty Theme name field by
adding some text, then the binding of C-x C-s mysteriously
changes to ‘save-buffer’.
2. Sometimes when point is on the Theme name or Description
field, then Custom is added to the menu line, but it isn’t
added to the menu the first time that point is put on those
fields.
3. Sometimes point disappears and cannot be restored. Is this
a problem with Emacs’s code or with the window manager? Not
all Emacs versions are alike due to different graphics
libraries with which Emacs is built.
--
The lyf so short, the craft so long to lerne.
- Geoffrey Chaucer, The Parliament of Birds.
lmpx.com only provides a reader for public news (NNTP) servers. It is not
affiliated with the servers or forums shown here and is not responsible for
the content of articles, which is written by their respective authors.