From: Drew Adams <drew.adams@oracle.com>
To: Marcin Borkowski <mbork@mbork.pl>
Cc: 19107@debbugs.gnu.org
Subject: bug#19107: 25.0.50; emacs-lisp-mode: help-echo in font-lock-extra-managed-props
Date: Fri, 11 Mar 2016 07:57:00 -0800 (PST) [thread overview]
Message-ID: <8fea3afa-9951-4991-99c5-68d7a6f152ff@default> (raw)
In-Reply-To: <87io0tw9ka.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.
>
> OK. I didn't know (and still don't) what help-echo is for, hence my
> question. (And I even don't know how to ask Emacs that question, aside
> from grepping the source.)
`C-h i' Elisp
`i help-echo TAB' shows you these nodes:
1. help-echo (overlay property)
2. help-echo (text property)
3. help-echo, customization keyword
4. 'help-echo' event
(Visiting #1 also presents a link to node `Text help-echo', which
is apparently misdirected. See bug #22986.)
(TAB will not show you #4 unless you have substring completion.
See bug #22987. I use Icicles and `S-TAB' to see the candidates.)
If you visit those nodes you will learn how `help-echo' is used and
how you can use it yourself in your code. If you find that the doc
for this is not clear enough please consider filing a bug report to
improve it. Thx.
next prev parent reply other threads:[~2016-03-11 15:57 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
2016-03-11 11:14 ` Marcin Borkowski
2016-03-11 15:57 ` Drew Adams [this message]
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=8fea3afa-9951-4991-99c5-68d7a6f152ff@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).