From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 43396@debbugs.gnu.org, tlikonen@iki.fi
Subject: bug#43396: 27.1; Customized "cursor" face has no effect in daemon mode
Date: Wed, 30 Jun 2021 15:29:36 +0300 [thread overview]
Message-ID: <83wnqbmt73.fsf@gnu.org> (raw)
In-Reply-To: <87fswz8s71.fsf@gnus.org> (message from Lars Ingebrigtsen on Wed, 30 Jun 2021 14:14:58 +0200)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: Teemu Likonen <tlikonen@iki.fi>, 43396@debbugs.gnu.org
> Date: Wed, 30 Jun 2021 14:14:58 +0200
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > Yes, we have a design bug here (and in some other places):
> > customizations that need GUI features don't work well when invoked at
> > startup time in daemon sessions. If someone knows how to fix
> > custom-set-faces so that the face is re-evaluated when the first GUI
> > frame is created, patches and/or ideas are welcome.
>
> Yeah, it's a tricky problem... unless we just add some brute-forcing of
> this when the first graphical frame is created.
>
> That is, we just go through all the faces that have been created already
> (with `custom-set-faces') when the user eventually creates a frame, and
> then re-evaluate everything.
We have custom-reevaluate-setting, but I think it only works on
variables. And we lack a mechanism that would perform re-evaluation
of faces that were customized.
> Uhm... perhaps we could have a `custom-reset-faces' function that
> people can put in a server/client hook to achieve this if they want to?
That could be a sufficient stop-gap solution, IMO.
prev parent reply other threads:[~2021-06-30 12:29 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-14 13:23 bug#43396: 27.1; Customized "cursor" face has no effect in daemon mode Teemu Likonen
2020-09-14 15:33 ` Eli Zaretskii
2020-09-14 15:58 ` Teemu Likonen
2021-06-12 12:22 ` Lars Ingebrigtsen
2021-06-12 12:47 ` Eli Zaretskii
2021-06-13 7:56 ` Eli Zaretskii
2021-06-28 10:09 ` Teemu Likonen
2021-06-28 11:54 ` Eli Zaretskii
2021-06-28 12:51 ` Teemu Likonen
2021-06-28 14:53 ` Eli Zaretskii
2021-06-28 17:07 ` Teemu Likonen
2021-06-28 17:24 ` Eli Zaretskii
2021-06-28 18:47 ` Teemu Likonen
2021-06-29 12:21 ` Eli Zaretskii
2021-06-29 13:38 ` Teemu Likonen
2021-06-30 12:14 ` Lars Ingebrigtsen
2021-06-30 12:29 ` Eli Zaretskii [this message]
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=83wnqbmt73.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=43396@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=tlikonen@iki.fi \
/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).