From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 34715@debbugs.gnu.org, 32736@debbugs.gnu.org
Subject: bug#32736: bug#34715: bug#32736: 26; Bind `C-x 5 2' to `clone-frame' by default
Date: Thu, 02 Sep 2021 15:03:58 +0300 [thread overview]
Message-ID: <83mtovnpzl.fsf@gnu.org> (raw)
In-Reply-To: <87mtov73t7.fsf@gnus.org> (message from Lars Ingebrigtsen on Thu, 02 Sep 2021 10:57:24 +0200)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: 34715@debbugs.gnu.org, 32736@debbugs.gnu.org
> Date: Thu, 02 Sep 2021 10:57:24 +0200
>
> >> > And the faces aren't copied, I think, they reference the same faces
> >> > the original frame had.
> >>
> >> Right -- I don't really know how the face/frame stuff actually works.
> >> If it was a very general problem, then surely we'd stumble across this
> >> whenever we make a new frame. But the bug seems to manifest only on
> >> terminal frames -- when we change the background mode.
> >
> > That's true, but it doesn't mean we don't have a deeper problem.
>
> True. I'll continue to debug this, but won't have time today, I
> think... If you want to have a look meanwhile, please go ahead. :-)
> It reproduces easily, and the bug seems to be caused by something called
> by `frame-set-background-mode', but that may or may not be correct
> (perhaps it's just doing something that triggers the real problem caused
> somewhere else).
I think I fixed this. The problem was indeed with letting the new
frame manipulate a separate set of faces: we arrange for that in
make-terminal-frame, but we were doing that a tad too late.
next prev parent reply other threads:[~2021-09-02 12:03 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-03 0:47 bug#34715: 26.1; (1) Add `clone-frame', (2) bind it to `C-x 5 2' Drew Adams
2019-03-04 16:12 ` Eli Zaretskii
2019-03-08 9:46 ` Eli Zaretskii
2021-09-01 9:43 ` bug#32736: 26; Bind `C-x 5 2' to `clone-frame' by default Lars Ingebrigtsen
2021-09-01 12:47 ` bug#34715: " Eli Zaretskii
2021-09-01 12:53 ` bug#32736: " Lars Ingebrigtsen
2021-09-01 13:38 ` Eli Zaretskii
2021-09-01 13:40 ` Lars Ingebrigtsen
2021-09-01 13:41 ` Lars Ingebrigtsen
2021-09-01 13:55 ` Lars Ingebrigtsen
2021-09-01 14:11 ` Eli Zaretskii
2021-09-01 14:18 ` Lars Ingebrigtsen
2021-09-01 14:28 ` bug#34715: " Lars Ingebrigtsen
2021-09-01 15:57 ` Eli Zaretskii
2021-09-02 7:44 ` Lars Ingebrigtsen
2021-09-02 7:51 ` Eli Zaretskii
2021-09-02 8:01 ` bug#34715: " Lars Ingebrigtsen
2021-09-02 8:19 ` Eli Zaretskii
2021-09-02 8:57 ` Lars Ingebrigtsen
2021-09-02 12:03 ` Eli Zaretskii [this message]
2021-09-02 16:05 ` bug#34715: " Lars Ingebrigtsen
[not found] <<17bef02b-7dd4-4086-828f-59488a836ac1@default>
[not found] ` <<83sgw2ehzu.fsf@gnu.org>
2019-03-04 17:25 ` bug#34715: 26.1; (1) Add `clone-frame', (2) bind it to `C-x 5 2' Drew Adams
2019-03-04 18:14 ` Eli Zaretskii
2019-03-30 21:58 ` Juri Linkov
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=83mtovnpzl.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=32736@debbugs.gnu.org \
--cc=34715@debbugs.gnu.org \
--cc=larsi@gnus.org \
/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).