From: Lars Ingebrigtsen <larsi@gnus.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 27517@debbugs.gnu.org, Vitalie Spinu <spinuvit@gmail.com>
Subject: bug#27517: 26.0.50; 25.2.2; Cannot add "help-echo" property to buffer regions in *lisp-mode
Date: Sat, 14 Aug 2021 14:03:24 +0200 [thread overview]
Message-ID: <8735rcutbn.fsf@gnus.org> (raw)
In-Reply-To: <jwvy2959m07.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Fri, 13 Aug 2021 23:06:38 -0400")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
> There is sadly no easy way to do that currently.
> You can do things like:
> - Use an overlay instead of a text-property.
> - Apply the text-property via `font-lock-add-keywords` rather than directly.
Hm, yes...
> - Add support for "multiple planes" in text-properties. This means that
> font-lock would use its own "plane" and your package could use another
> plane, and the two would be correctly merged and font-lock wouldn't
> erase your properties.
Oh, yeah! I'd totally forgotten -- that would indeed be the long term
fix for these issues. I think there's an issue for that somewhere in
here...
In any case, I'm closing this report, because it's basically "working as
designed" (until we get a new design).
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
prev parent reply other threads:[~2021-08-14 12:03 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
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 [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
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=8735rcutbn.fsf@gnus.org \
--to=larsi@gnus.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).