From: Dmitry Gutov <dmitry@gutov.dev>
To: Po Lu <luangruo@yahoo.com>, Eli Zaretskii <eliz@gnu.org>
Cc: gerd.moellmann@gmail.com, emacs-devel@gnu.org
Subject: Re: Q: child frames on ttys
Date: Mon, 16 Sep 2024 04:35:56 +0300 [thread overview]
Message-ID: <ee1b7cb0-c62b-4853-90b3-3b4609057f39@gutov.dev> (raw)
In-Reply-To: <be572c6d-b857-4639-9c03-574cfad0409f@gutov.dev>
On 01/09/2024 03:27, Dmitry Gutov wrote:
> On 31/08/2024 11:46, Po Lu wrote:
>>>> Off topic (sorry), but I wish someone worked on child frames looking
>>>> better under GNOME/Linux.
>>>>
>>>> When I test it on macOS, it seems regular, but under GNOME it swiftly
>>>> blinks once every refresh. Something to do with double buffering,
>>>> maybe.
>>> Do you mean that disabling double-buffering stops the blinking?
>> Any issue observed with child frames should first be reproduced on a
>> build `--with-x-toolkit=no', or there's no eliminating the toolkit as a
>> suspect.
>
> It's reproducible with the "no toolkit" build just the same, see the
> recording in the other email that I made with it.
Correction: I see the issue with the "lucid" build, a slightly different
visually but also buggy behavior with the "no toolkit" build (I think
that's the one I made the video with), and actually no problem with the
"gtk3" build (in the past the variable x-gtk-resize-child-frames was
added as a workaround, but on my current system it does not seem to
matter -- maybe because it's using Wayland).
The pgtk build is almost fine, but "blinks" about 1 time out of 20.
next prev parent reply other threads:[~2024-09-16 1:35 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-17 7:24 Q: child frames on ttys Gerd Möllmann
2024-08-17 10:39 ` Eli Zaretskii
2024-08-17 11:02 ` Gerd Möllmann
2024-08-17 17:18 ` martin rudalics
2024-08-17 18:41 ` Gerd Möllmann
2024-08-21 7:10 ` Gerd Möllmann
2024-08-21 7:55 ` martin rudalics
2024-08-21 8:03 ` Gerd Möllmann
2024-08-21 8:11 ` Robert Pluim
2024-08-21 8:38 ` Gerd Möllmann
2024-08-21 12:00 ` Gerd Möllmann
2024-08-30 6:42 ` Gerd Möllmann
2024-08-30 9:17 ` martin rudalics
2024-08-30 11:03 ` Eli Zaretskii
2024-08-30 11:23 ` Gerd Möllmann
2024-08-30 14:53 ` Eli Zaretskii
2024-08-31 8:26 ` Gerd Möllmann
2024-08-31 11:54 ` Eli Zaretskii
2024-08-31 14:00 ` Gerd Möllmann
2024-08-31 14:40 ` Eli Zaretskii
2024-09-02 8:37 ` Gerd Möllmann
2024-09-02 11:38 ` Eli Zaretskii
2024-09-02 12:46 ` Gerd Möllmann
2024-09-02 13:13 ` Eli Zaretskii
2024-09-02 13:54 ` Gerd Möllmann
2024-08-30 11:09 ` Gerd Möllmann
2024-08-30 9:29 ` Robert Pluim
2024-08-30 11:19 ` Gerd Möllmann
2024-08-30 12:00 ` Robert Pluim
2024-08-30 12:37 ` Gerd Möllmann
2024-08-30 21:11 ` Dmitry Gutov
2024-08-31 6:45 ` Eli Zaretskii
2024-08-31 8:46 ` Po Lu
2024-09-01 0:27 ` Dmitry Gutov
2024-09-16 1:35 ` Dmitry Gutov [this message]
2024-09-01 0:27 ` Dmitry Gutov
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=ee1b7cb0-c62b-4853-90b3-3b4609057f39@gutov.dev \
--to=dmitry@gutov.dev \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=gerd.moellmann@gmail.com \
--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).