GNU bug report logs - #54156
28.0.91; set-face-attribute with a nil FRAME doesn't change the default

Previous Next

Full log

View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Drew Adams <drew.adams <at> oracle.com>
Cc: damien <at> cassou.me, larsi <at> gnus.org, 54156 <at> debbugs.gnu.org
Subject: bug#54156: [External] : bug#54156: 28.0.91; set-face-attribute with a nil FRAME doesn't change the default
Date: Sat, 26 Feb 2022 19:50:39 +0200

> From: Drew Adams <drew.adams <at> oracle.com>
> CC: "larsi <at> gnus.org" <larsi <at> gnus.org>, "damien <at> cassou.me" <damien <at> cassou.me>,
>         "54156 <at> debbugs.gnu.org" <54156 <at> debbugs.gnu.org>
> Date: Sat, 26 Feb 2022 17:23:22 +0000
> 
> > I'm not sure this isn't the result of the particular implementation we
> > have, so I prefer to tell people to call with FRAME = t explicitly.
> > After all, this is a rare use case.
> 
> But is what I said correct, that just using nil
> as the frame makes both the existing frames and
> future ones use `unspecified' as the face value?

If you use 'unspecified', yes.

> And using _only_ `t' doesn't set the attribute
> to `unspecified' for the existing frames, right?

I didn't say to use only t.

> > We generally don't advertise compatibility shims for obsolete
> > features, because we want people to stop using them.
> 
> Is it declared to be obsolete?

It's considered unsupported.  We just silently support it for
compatibility with old versions.

Previous Next

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