unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Marcin Borkowski <mbork@mbork.pl>, 19107@debbugs.gnu.org
Subject: bug#19107: 25.0.50; emacs-lisp-mode: help-echo in font-lock-extra-managed-props
Date: Wed, 9 Mar 2016 06:42:41 -0800 (PST)	[thread overview]
Message-ID: <80a4e3ea-421e-41ce-82c5-e8d6261834c6@default> (raw)
In-Reply-To: <87a8m8xjjh.fsf@mbork.pl>

> I confirm this is apparently still true on ac9a931, but I don't see why
> it's a problem.  Could you elaborate a bit?  What exactly breaks?  What
> is your non-font-lock use of help-echo?

Marcin, are you actually asking whether `help-echo' can or
should be used without font-lock?  If so, the answer is YES.

Text properties (including `face' and even `font-lock-face',
BTW) have nothing, per se, to do with `font-lock-mode'.
Font-lock is only one user of text properties.  Users and
code can use any properties in any way.

And property `help-echo', in particular, is used far and
wide outside of any use font-lock might make of it.

(As for the bug, I have nothing particular to say.  And your
question about what breaks is reasonable.  But keep in mind
that anything (font-lock or anything else) that assumes or
acts like it owns property `help-echo' is acting irresponsibly
and is bound to lead to bugs.)





  reply	other threads:[~2016-03-09 14:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-19 15:29 bug#19107: 25.0.50; emacs-lisp-mode: help-echo in font-lock-extra-managed-props Christopher Schmidt
2016-03-09  6:16 ` Marcin Borkowski
2016-03-09 14:42   ` Drew Adams [this message]
2016-03-11 11:14     ` Marcin Borkowski
2016-03-11 15:57       ` Drew Adams
2019-10-30 15:01 ` Lars Ingebrigtsen

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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=80a4e3ea-421e-41ce-82c5-e8d6261834c6@default \
    --to=drew.adams@oracle.com \
    --cc=19107@debbugs.gnu.org \
    --cc=mbork@mbork.pl \
    /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 public inbox

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).