From: martin rudalics <rudalics@gmx.at>
To: Tassilo Horn <tsdh@gnu.org>, Po Lu <luangruo@yahoo.com>
Cc: Lars Ingebrigtsen <larsi@gnus.org>, emacs-devel@gnu.org
Subject: Re: master 6e5d79c048: Display show-paren-context-when-offscreen in child frame
Date: Tue, 8 Feb 2022 10:01:32 +0100 [thread overview]
Message-ID: <fa283152-38d2-f360-bfd2-670b97eae960@gmx.at> (raw)
In-Reply-To: <8735ktzve1.fsf@gnu.org>
> I've tried but only found this one:
>
> bug#52677: 29.0.50; make-frame-visible/invisible too slow when use --with-pgtk
>
> Anyhow, I think being able to toggle a frame's visibility state on/off
> only ten times a second isn't so horrible slow.
From my experience, it's usually very hard to get more information from
tumashu so I won't try. But we'd first of all have to know (1) whether
this slowness happens on Wayland only and (2) whether normal (non-child)
frames are affected too.
> Of course, it depends
> on use-case. But for show-paren where there's `show-paren-delay' anyhow
> it doesn't really matter from my POV.
>
> FWIW, I don't have posframe installed but tried this benchmark which is
> quite similar:
>
> (benchmark 10
> '(show-paren--show-context-in-child-frame "foobar"))
> ;Elapsed time: 1.178163s (0.047553s in 3 GCs)
Does that make the child frame invisible in between? If not, you're
comparing apples and oranges
martin
next prev parent reply other threads:[~2022-02-08 9:01 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
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 [this message]
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=fa283152-38d2-f360-bfd2-670b97eae960@gmx.at \
--to=rudalics@gmx.at \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.org \
--cc=luangruo@yahoo.com \
--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).