unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Damien Cassou <damien@cassou.me>
Cc: 54156@debbugs.gnu.org
Subject: bug#54156: 28.0.91; set-face-attribute with a nil FRAME doesn't change the default
Date: Fri, 25 Feb 2022 14:16:01 +0200	[thread overview]
Message-ID: <83ilt3qgzi.fsf@gnu.org> (raw)
In-Reply-To: <87ilt3456u.fsf@cassou.me> (message from Damien Cassou on Fri, 25 Feb 2022 11:21:45 +0100)

> From: Damien Cassou <damien@cassou.me>
> Date: Fri, 25 Feb 2022 11:21:45 +0100
> 
> I have this in my init.el file:
> 
> (set-face-attribute 'finsit-javascript-html-tag-face nil :background nil)
> 
> As you can see, the FRAME argument (the 2nd) is nil. The documentation
> says: "If FRAME is nil, set the attributes for all existing frames, as
> well as the default for new frames.".
> 
> However, when creating a new frame the background of this face is
> reset and I have to execute this line manually.

Please show a complete recipe for reproducing the problem, starting
from "emacs -Q".  In particular, we need to see:

  . how that face was defined in the first place (defface or somesuch)
  . how you create a new frame

> Workaround:
> 
>   (defun my/fix-finsit-javascript-html-tag-face ()
>     "Remove the background of `finsit-javascript-html-tag-face'."
>     (set-face-attribute 'finsit-javascript-html-tag-face nil :background nil))
> 
>   (add-hook 'server-after-make-frame-hook #'my/fix-finsit-javascript-html-tag-face)

Since you set 'server-after-make-frame-hook', does this mean the
problem happens only with emacsclient frames?  If so, that is one more
reason for providing a complete recipe for us to investigate.

Thanks.





      parent reply	other threads:[~2022-02-25 12:16 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-25 10:21 bug#54156: 28.0.91; set-face-attribute with a nil FRAME doesn't change the default Damien Cassou
2022-02-25 12:15 ` Lars Ingebrigtsen
2022-02-25 12:26   ` Eli Zaretskii
2022-02-25 12:30     ` Lars Ingebrigtsen
2022-02-25 13:03       ` Eli Zaretskii
2022-02-25 13:12         ` Lars Ingebrigtsen
2022-02-25 13:24           ` Eli Zaretskii
2022-02-25 15:42             ` bug#54156: [External] : " Drew Adams
2022-02-26 15:04             ` Lars Ingebrigtsen
2022-02-26 15:24               ` Eli Zaretskii
2022-02-26 16:17                 ` bug#54156: [External] : " Drew Adams
2022-02-26 16:35                   ` Eli Zaretskii
2022-02-26 17:23                     ` Drew Adams
2022-02-26 17:50                       ` Eli Zaretskii
2022-02-26 22:47                         ` Drew Adams
2022-02-27  7:04                           ` Eli Zaretskii
2022-02-27 15:49                             ` Drew Adams
2022-02-27 13:02                 ` Lars Ingebrigtsen
2022-02-27 16:13                   ` bug#54156: [External] : " Drew Adams
2022-02-25 12:16 ` 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=83ilt3qgzi.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=54156@debbugs.gnu.org \
    --cc=damien@cassou.me \
    /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).