emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[debbugs-tracker] bug#24543: closed (25.1; describe-symbol doesn't show


From: GNU bug Tracking System
Subject: [debbugs-tracker] bug#24543: closed (25.1; describe-symbol doesn't show face with same name as a variable)
Date: Sat, 05 Aug 2017 08:54:01 +0000

Your message dated Sat, 05 Aug 2017 11:53:00 +0300
with message-id <address@hidden>
and subject line Re: bug#24543: 25.1; describe-symbol doesn't show face with 
same name as a variable
has caused the debbugs.gnu.org bug report #24543,
regarding 25.1; describe-symbol doesn't show face with same name as a variable
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
24543: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=24543
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: 25.1; describe-symbol doesn't show face with same name as a variable Date: Sun, 25 Sep 2016 12:49:11 -0600 User-agent: Gnus/5.13 (Gnus v5.13) Emacs/25.1 (gnu/linux)
Recipe:

emacs -Q
C-h o font-lock-comment-face RET

Only the variable of this name is shown, not the face (which can be
viewed with describe-face, of course).

It appears that when the face only shares a name with a function, then
both the function and face are shown. Only a variable shadows the face
in describe-symbol.



--- End Message ---
--- Begin Message --- Subject: Re: bug#24543: 25.1; describe-symbol doesn't show face with same name as a variable Date: Sat, 05 Aug 2017 11:53:00 +0300
> From: Alex <address@hidden>
> Cc: address@hidden
> Date: Fri, 28 Jul 2017 14:45:24 -0600
> 
> > if so, could it break some of the users of this function out there?
> 
> Potentially, but I don't see that being an issue in this case. The
> return value isn't documented, so users shouldn't be (and likely aren't)
> relying on describe-face always returning nil. It makes more sense to
> treat describe-face like describe-{function, variable}.

OK, I pushed the changes.

Thanks.


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]