From: Eli Zaretskii <eliz@gnu.org>
To: martin rudalics <rudalics@gmx.at>
Cc: alexanderm@web.de, 40639@debbugs.gnu.org
Subject: bug#40639: 26.3; Child frame border color not rendered when child frame has no minibuffer
Date: Wed, 15 Apr 2020 20:32:33 +0300 [thread overview]
Message-ID: <83ftd4fydq.fsf@gnu.org> (raw)
In-Reply-To: <ab39a882-3dc9-6b3c-7cbb-441fdb96104f@gmx.at> (message from martin rudalics on Wed, 15 Apr 2020 19:20:45 +0200)
> From: martin rudalics <rudalics@gmx.at>
> Date: Wed, 15 Apr 2020 19:20:45 +0200
>
> int face_id =
> !NILP (Vface_remapping_alist)
> ? lookup_basic_face (NULL, f, INTERNAL_BORDER_FACE_ID)
> : INTERNAL_BORDER_FACE_ID;
> struct face *face = FACE_FROM_ID_OR_NULL (f, face_id);
>
> block_input ();
>
> if (face)
> {
> unsigned long color = face->background;
>
> the value of color for a new normal frame is for a few calls white but
> switches to red before the frame appears on the display. A child frame
> usually must be explicitly focused before its border becomes red (I
> don't necessarily need the mouse for that purpose, C-x 5 o works too).
>
> Maybe our experts in face remapping have an idea.
I don't think face mapping is directly involved, this sounds like some
X event causes the change.
next prev parent reply other threads:[~2020-04-15 17:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-15 10:10 bug#40639: 26.3; Child frame border color not rendered when child frame has no minibuffer Alexander Miller
2020-04-15 17:20 ` martin rudalics
2020-04-15 17:32 ` Eli Zaretskii [this message]
2020-04-16 8:31 ` martin rudalics
2020-04-18 8:51 ` martin rudalics
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=83ftd4fydq.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=40639@debbugs.gnu.org \
--cc=alexanderm@web.de \
--cc=rudalics@gmx.at \
/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).