unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Vladimir Kazanov <vekazanov@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: [PATCH] User-defined fringe tooltips (a request for review)
Date: Mon, 25 Mar 2024 19:11:41 +0200	[thread overview]
Message-ID: <86frwejkxe.fsf@gnu.org> (raw)
In-Reply-To: <CAAs=0-2cCCJe-4RKfMJ8FkmzjnCSdf8CMhuG54RAh270ivEchA@mail.gmail.com> (message from Vladimir Kazanov on Mon, 25 Mar 2024 15:55:16 +0000)

> From: Vladimir Kazanov <vekazanov@gmail.com>
> Date: Mon, 25 Mar 2024 15:55:16 +0000
> Cc: emacs-devel@gnu.org
> 
> The code in the (note_fringe_highlight) function works outside of the
> main (handle_single_display_spec) call. So to get to the :help-echo
> string it has to parse into the spec, or a list of specs, or a vector
> of specs, effectively duplicating parsing logic in
> handle_single_display_spec. This is not nice but doable.
> 
> But every display spec can be wrapped in a (when CONDITION . SPEC)
> form. And because (handle_single_display_spec) happens at a time
> different from the (note_fringe_highlight) call time we can never be
> sure that the condition still holds even if the code reevaluates
> CONDITION.

The condition is only evaluated at glyph generation time, as for any
other display property.  When the tooltip should be displayed, the
condition is not relevant, since if it were false when the glyphs were
generated, you wouldn't have had the fringe bitmap shown in the first
place.

However, I think there's an easy way of making the implementation
easier: just introduce a new overlay property called, say,
fringe-help-echo, and put that property on the same text as the
display property which produces the fringe.  Then the code in
note_fringe_highlight should simply check if the text which yielded
the fringe bitmap also has this special property on it, and if so,
display the tooltip.



  reply	other threads:[~2024-03-25 17:11 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-19 19:38 [PATCH] User-defined fringe tooltips (a request for review) Vladimir Kazanov
2023-12-20 12:31 ` Eli Zaretskii
2023-12-21 16:51   ` Vladimir Kazanov
2023-12-21 17:37     ` Eli Zaretskii
2023-12-23 13:28       ` Vladimir Kazanov
2023-12-23 13:40         ` Eli Zaretskii
2023-12-24 11:31           ` Vladimir Kazanov
2023-12-24 16:54             ` Eli Zaretskii
2024-03-25 15:55               ` Vladimir Kazanov
2024-03-25 17:11                 ` Eli Zaretskii [this message]
2024-03-26 22:16                   ` Vladimir Kazanov
2024-03-27 10:59                     ` Vladimir Kazanov
2024-03-27 11:25                       ` Po Lu
2024-03-27 12:48                         ` Vladimir Kazanov
2024-03-27 11:25                       ` Po Lu
2024-03-31  8:36                       ` Eli Zaretskii
2024-04-07 11:14                         ` Vladimir Kazanov
2024-04-07 12:44                           ` Eli Zaretskii
2024-04-07 17:07                             ` Vladimir Kazanov
2024-04-07 18:40                               ` Eli Zaretskii
2024-04-08 14:41                                 ` Vladimir Kazanov
2024-04-13  9:14                                   ` Eli Zaretskii
2024-04-13  9:32                                     ` Vladimir Kazanov
2024-04-13 11:21                                       ` Eli Zaretskii
2024-04-13 14:53                                         ` Vladimir Kazanov
2024-04-13 15:47                                           ` Eli Zaretskii
2024-03-27 12:14                     ` Eli Zaretskii
2024-03-27 12:48                       ` Vladimir Kazanov

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=86frwejkxe.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=vekazanov@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).