From: Eli Zaretskii <eliz@gnu.org>
To: tlikonen@iki.fi
Cc: 43396@debbugs.gnu.org, larsi@gnus.org
Subject: bug#43396: 27.1; Customized "cursor" face has no effect in daemon mode
Date: Sun, 13 Jun 2021 10:56:40 +0300 [thread overview]
Message-ID: <83tum26vuv.fsf@gnu.org> (raw)
In-Reply-To: <83eed78d1z.fsf@gnu.org> (message from Eli Zaretskii on Sat, 12 Jun 2021 15:47:36 +0300)
> Date: Sat, 12 Jun 2021 15:47:36 +0300
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: 43396@debbugs.gnu.org, tlikonen@iki.fi
>
> > > I think you need to do that in server-after-make-frame-hook instead,
> > > to make it work in a daemon session. When the daemon reads your init
> > > file, it doesn't have a GUI frame to play with, so some
> > > display-related customizations don't work until there's a frame.
> >
> > Is this a bug, or just how this has to work?
>
> Frankly, I'm not sure. Given the workaround the OP posted, it sounds
> like it could be a subtle bug somewhere: custom-set-faces doesn't seem
> to call face-set-spec in the daemon case.
First thing I'd like to know is: when the first GUI frame is created
by that daemon, is there a 'cursor-color' frame parameter in that
frame's parameters list?
next prev parent reply other threads:[~2021-06-13 7:56 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 [this message]
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
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=83tum26vuv.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).