GNU bug report logs - #34715
26.1; (1) Add `clone-frame', (2) bind it to `C-x 5 2'

Previous Next

Full log

Message #57 received at 34715 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Lars Ingebrigtsen <larsi <at> gnus.org>
Cc: 34715 <at> debbugs.gnu.org, 32736 <at> debbugs.gnu.org
Subject: Re: bug#32736: bug#34715: bug#32736: 26; Bind `C-x 5 2' to
 `clone-frame' by default
Date: Wed, 01 Sep 2021 18:57:23 +0300

> From: Lars Ingebrigtsen <larsi <at> gnus.org>
> Cc: 34715 <at> debbugs.gnu.org,  32736 <at> debbugs.gnu.org
> Date: Wed, 01 Sep 2021 16:18:13 +0200
> 
> Eli Zaretskii <eliz <at> gnu.org> writes:
> 
> > If the problem is background-color, why does redisplay complain about
> > faces saying they are *invalid*?  I could understand if it said it
> > cannot load some color, but why "invalid face"?
> >
> > The only funky thing about background-color on TTY I can think of is
> > the unspecified-bg thingy.
> 
> The following is the minimal case for reproduction here:
> 
> (let ((default-frame-alist
>         '((background-color . "red"))))
>   (make-frame))
> 
> This reliably makes all the faces go AWOL on the new frame.  (It doesn't
> matter what the colour is.)

Shouldn't we copy the parameters alist?  Maybe even deep-copy?  And
faces are supposed to be frame-local, so maybe faces also need to be
copied?  Otherwise, you are basically manipulating faces that don't
"belong" to the frame, no?  And likewise with frame's parameters
alist, I think.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.