all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "E. Choroba" <choroba@matfyz.cz>
Cc: 33421@debbugs.gnu.org
Subject: bug#33421: 26.1; hl-line face used as default
Date: Mon, 19 Nov 2018 17:45:09 +0200	[thread overview]
Message-ID: <83y39prrzu.fsf@gnu.org> (raw)
In-Reply-To: <alpine.LSU.2.20.1811182235420.3193@fgvyy.zf.zss.phav.pm> (choroba@matfyz.cz)

tags 33421 notabug
thanks

> Date: Sun, 18 Nov 2018 22:37:57 +0100 (CET)
> From: "E. Choroba" <choroba@matfyz.cz>
> 
> When I use emacs 24.3.1 and run
> 
>    /usr/bin/emacs -Q
> 
> Then M-< followed by M-x global-hl-line-mode and M-x describe-face, emacs asks 
> me
> 
> Describe face (default `font-lock-comment-delimiter-face'):
> 
> But when I use 26.1 and run
> 
>    /usr/local/bin/emacs -Q
> 
> and run exactly the same commands, emacs asks me
> 
> Describe face (default ‘hl-line’):
> 
> I have to turn hl-line off to get the name of the point's face. This makes the 
> default value of the function useless.

I can reproduce this, but for me both Emacs 26 and Emacs 24 behave the
same.  So I don't know why your Emacs 24 behaves differently, perhaps
it's due to some local changes that are not in upstream sources.

In any case, "M-x describe-face" is not the right tool when there
could be several text properties at the same position, because
describe-face can only name one face, and it selects the one that
affects the text the most.  I suggest to use another command instead,
"M-x describe-text-properties".  It will pop up a window with
information about all the properties at point, and you can then drill
down using the buttons in that window.

This is not a bug.

Thanks.





      reply	other threads:[~2018-11-19 15:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-18 21:37 bug#33421: 26.1; hl-line face used as default E. Choroba
2018-11-19 15:45 ` Eli Zaretskii [this message]

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83y39prrzu.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=33421@debbugs.gnu.org \
    --cc=choroba@matfyz.cz \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.