GNU bug report logs - #57499
Documentation bug in the docstring of set-face-attribute?

Previous Next

Full log

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

From: Eli Zaretskii <eliz <at> gnu.org>
To: Gregory Heytings <gregory <at> heytings.org>
Cc: 57499 <at> debbugs.gnu.org
Subject: Re: bug#57499: Documentation bug in the docstring of
 set-face-attribute?
Date: Wed, 31 Aug 2022 14:11:51 +0300

> Date: Wed, 31 Aug 2022 08:14:00 +0000
> From: Gregory Heytings <gregory <at> heytings.org>
> 
> 
> The docstring of set-face-attribute says:
> 
> "As an exception, to reset the value of some attribute to `unspecified' in 
> a way that overrides the non-`unspecified' value defined by the face's 
> spec in `defface', for new frames, you must explicitly call this function 
> with FRAME set to t and the attribute's value set to `unspecified'; just 
> using FRAME of nil will not affect new frames in this case."
> 
> Not only is that sentence hard to parse, it also seems wrong.
> 
> Can someone come up with a scenario in which a call
> 
> (set-face-attribute 'some-face nil :some-attribute 'unspecified)
> 
> only affects existing frames?  In my testing it affects all frames 
> (existing and future ones), and that's also what the code seems to do: 
> set-face-attribute sets where to 0 when frame is nil, and calls 
> internal-set-face-attribute

This was discussed in bug#54156.  Are there any new findings or
considerations that would require to reopen that discussion?

Previous Next

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