From: Eli Zaretskii <eliz@gnu.org>
To: Vitalie Spinu <spinuvit@gmail.com>,
Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 27517@debbugs.gnu.org
Subject: bug#27517: 26.0.50; 25.2.2; Cannot add "help-echo" property to buffer regions.
Date: Wed, 28 Jun 2017 19:38:32 +0300 [thread overview]
Message-ID: <83shikqd87.fsf@gnu.org> (raw)
In-Reply-To: <87efu4l284.fsf@galago> (message from Vitalie Spinu on Wed, 28 Jun 2017 14:35:07 +0200)
> From: Vitalie Spinu <spinuvit@gmail.com>
> Date: Wed, 28 Jun 2017 14:35:07 +0200
>
> (put-text-property (point-min) 100 'help-echo "my-mouse-over" (current-buffer))
>
> No "help-ehco" property is added. Any other property (including special
> properties) can be added.
But only in lisp-mode, right?
This happens because lisp-mode.el wants itself to manage the help-echo
property:
(defun lisp-mode-variables (&optional lisp-syntax keywords-case-insensitive
elisp)
...
(setq font-lock-defaults
`(,(if elisp '(lisp-el-font-lock-keywords
lisp-el-font-lock-keywords-1
lisp-el-font-lock-keywords-2)
'(lisp-cl-font-lock-keywords
lisp-cl-font-lock-keywords-1
lisp-cl-font-lock-keywords-2))
nil ,keywords-case-insensitive nil nil
(font-lock-mark-block-function . mark-defun)
(font-lock-extra-managed-props help-echo)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
When a property appears in font-lock-extra-managed-props, font-lock
removes that property when it's about to re-fontify some region, see
font-lock-default-unfontify-region.
CC'ing Stefan, who made that change.
next prev parent reply other threads:[~2017-06-28 16:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-28 12:35 bug#27517: 26.0.50; 25.2.2; Cannot add "help-echo" property to buffer regions Vitalie Spinu
2017-06-28 16:38 ` Eli Zaretskii [this message]
2017-06-28 22:22 ` Vitalie Spinu
2021-08-13 13:18 ` bug#27517: 26.0.50; 25.2.2; Cannot add "help-echo" property to buffer regions in *lisp-mode Lars Ingebrigtsen
2021-08-14 3:06 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-08-14 12:03 ` 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=83shikqd87.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=27517@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=spinuvit@gmail.com \
/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).