all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: Lars Ingebrigtsen <larsi@gnus.org>, 18343@debbugs.gnu.org
Subject: bug#18343: 24.4.50; REGRESSION: `help-echo' property is not added, so no tooltip or echo
Date: Sun, 1 May 2016 08:52:58 -0800 (GMT-08:00)	[thread overview]
Message-ID: <6e92c530-40e9-462d-b0bf-46911ac4a103@default> (raw)
In-Reply-To: <87a8k93fz7.fsf@web.de>

> > Why should `help-echo' be on `font-lock-extra-managed-props'?
> 
> I guess the reason is to allow font-lock to propertize parts of the
> buffer with this property.  This issue is a (presumably not trivially
> avoidable) side effect.

By "allow font-lock to propertize parts of the buffer with this
property" do you mean allow it to propertize, with faces, parts
of the buffer that happen to have property `help-echo'?  Or do
you mean allow it to add property `help-echo' parts of the buffer?

If the latter, what is the use case for font-lock doing that?

I'll assume you meant the former -

In that case, why not trivially avoidable?  Why not tell font-lock
hands-off this property, which has nothing to do with highlighting?
Until the recent change that caused this regression, property
`help-echo' was not on the list `font-lock-extra-managed-props'.

Is it clear to you why it needs to be on that list?  It's not
clear to me.





  reply	other threads:[~2016-05-01 16:52 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <<73dcc1a9-eab9-4f13-be3a-8e8eea6a2e8b@default>
     [not found] ` <<83vbpcin5h.fsf@gnu.org>
2014-08-28 17:06   ` bug#18343: 24.4.50; REGRESSION: `help-echo' property is not added, so no tooltip or echo Drew Adams
2014-08-28 17:20     ` Wolfgang Jenkner
2014-08-28 21:20       ` Drew Adams
2016-04-30 13:41     ` Lars Ingebrigtsen
2016-04-30 16:21       ` Drew Adams
2016-05-01 16:22         ` Michael Heerdegen
2016-05-01 16:52           ` Drew Adams [this message]
2016-05-01 17:08             ` Eli Zaretskii
2016-05-01 17:26             ` Michael Heerdegen
     [not found]           ` <<6e92c530-40e9-462d-b0bf-46911ac4a103@default>
     [not found]             ` <<83shy1n1t8.fsf@gnu.org>
2016-05-01 17:22               ` Drew Adams
2016-05-01 17:33                 ` Michael Heerdegen
2016-05-01 17:43                 ` Eli Zaretskii
2014-08-28 16:22 Drew Adams
2014-08-28 16:39 ` Eli Zaretskii
2014-08-28 16:52 ` Wolfgang Jenkner

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=6e92c530-40e9-462d-b0bf-46911ac4a103@default \
    --to=drew.adams@oracle.com \
    --cc=18343@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    --cc=michael_heerdegen@web.de \
    /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.