From: Po Lu <luangruo@yahoo.com>
To: Tassilo Horn <tsdh@gnu.org>
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: Thu, 10 Feb 2022 09:58:30 +0800 [thread overview]
Message-ID: <87sfsrzdmh.fsf@yahoo.com> (raw)
In-Reply-To: <87y22k15vw.fsf@gnu.org> (Tassilo Horn's message of "Wed, 09 Feb 2022 15:16:17 +0100")
Tassilo Horn <tsdh@gnu.org> writes:
> Tassilo Horn <tsdh@gnu.org> writes:
>
>>> BTW, if I press C-g while the overlay is displayed, it flickers but
>>> doesn't disappear.
>>
>> Hm, indeed, but it's the same for child-frame and also for "print in
>> the echo area". C-g-ing will also run `post-command-hook' which
>> removes the frame/overlay or prints Quit, but after `show-paren-delay'
>> the `show-paren--idle-timer' will trigger `show-paren-function' again
>> resulting in another overlay/frame/message.
>>
>> I'm not sure if that can be considered a bug but I can see that one
>> wants to be able to C-g away the overlay/child-frame, though. I guess
>> `show-paren-function' should track the current position of point and
>> not show context info if that has already been shown previously?
>
> I did that just now and it seems to work fine. Give it a try.
>
> Bye,
> Tassilo
Thanks, it seems to work nicely.
next prev parent reply other threads:[~2022-02-10 1:58 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 [this message]
2022-02-14 12:41 ` Po Lu
2022-02-14 13:41 ` Tassilo Horn
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=87sfsrzdmh.fsf@yahoo.com \
--to=luangruo@yahoo.com \
--cc=arash@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.org \
--cc=tsdh@gnu.org \
/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).