unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Tassilo Horn <tsdh@gnu.org>
To: Po Lu <luangruo@yahoo.com>
Cc: Arash Esbati <arash@gnu.org>, Lars Ingebrigtsen <larsi@gnus.org>,
	emacs-devel@gnu.org
Subject: Re: master 6e5d79c048: Display show-paren-context-when-offscreen in child frame
Date: Mon, 14 Feb 2022 14:41:39 +0100	[thread overview]
Message-ID: <87pmnp5yvl.fsf@gnu.org> (raw)
In-Reply-To: <87bkz9hb7w.fsf@yahoo.com>

Po Lu <luangruo@yahoo.com> writes:

> I found a problem: when I click so that point is moved onto the
> parentheses being highlighted, the context overlay flickers and then
> disappears.
>
> Any ideas?

Yes, after some poking, it seems that you get the intended behavior when
your mouse click is short, i.e., in that case, the behavior is the same
as if you've moved point to the closing paren with some non-mouse means.

However, when you press and hold the mouse button just a tiny bit
longer, I get the behavior you describe.

I guess the difference here is that in the first case, emacs handles
some "mouse button clicked" event whereas in the second case handles one
"mouse button pressed" and one "mouse button released" event.  "clicked"
and "pressed" seem to set point and will trigger the show-paren context
info but the "released" event then also runs `post-command-hook' which
will remove the context overlay/child-frame again.  And since we've
already shown the context info for the current position of point, we're
not gonna show it again.

I'm not sure how to fix that or even if it deserves a fix.

Bye,
Tassilo



  reply	other threads:[~2022-02-14 13:41 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <164414267475.11015.16458968298391656164@vcs2.savannah.gnu.org>
     [not found] ` <20220206101755.0EC03C002F9@vcs2.savannah.gnu.org>
2022-02-06 21:35   ` master 6e5d79c048: Display show-paren-context-when-offscreen in child frame Lars Ingebrigtsen
2022-02-07  1:28     ` Po Lu
2022-02-07  5:52       ` Tassilo Horn
2022-02-07 13:31         ` Arash Esbati
2022-02-07 14:08           ` Tassilo Horn
2022-02-07 15:45             ` Tassilo Horn
2022-02-07 18:13             ` Arash Esbati
2022-02-07 19:30               ` Tassilo Horn
2022-02-08  8:25                 ` Arash Esbati
2022-02-08  8:55                   ` Tassilo Horn
2022-02-09 12:45                   ` Tassilo Horn
2022-02-09 13:26                     ` Po Lu
2022-02-09 13:28                       ` Tassilo Horn
2022-02-09 13:42                         ` Po Lu
2022-02-09 13:45                           ` Tassilo Horn
2022-02-09 14:16                             ` Tassilo Horn
2022-02-10  1:58                               ` Po Lu
2022-02-14 12:41                               ` Po Lu
2022-02-14 13:41                                 ` Tassilo Horn [this message]
2022-02-09 13:50                         ` Arash Esbati
2022-02-09 18:22                       ` martin rudalics
2022-02-08  0:54         ` Po Lu
2022-02-08 12:00           ` Tassilo Horn
2022-02-08  1:43         ` Po Lu
2022-02-08  6:59           ` Tassilo Horn
2022-02-08  9:01             ` martin rudalics
2022-02-08  9:21               ` Po Lu
2022-02-08 10:06               ` Tassilo Horn

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=87pmnp5yvl.fsf@gnu.org \
    --to=tsdh@gnu.org \
    --cc=arash@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=larsi@gnus.org \
    --cc=luangruo@yahoo.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).