From: Gregory Heytings <gregory@heytings.org>
To: martin rudalics <rudalics@gmx.at>
Cc: Ash <ext0l@catgirl.ai>, Eli Zaretskii <eliz@gnu.org>,
65217@debbugs.gnu.org
Subject: bug#65217: 29.1; set-frame-size gets confused and drops calls
Date: Mon, 21 Aug 2023 08:30:11 +0000 [thread overview]
Message-ID: <77daee02cfc4d796b885@heytings.org> (raw)
In-Reply-To: <7a24940b-4d6e-7e7c-d81d-b9815e1d0fbb@gmx.at>
>
> The scroll bar is displayed and hidden repeatedly in either case- The
> surprising thing is that with GTK3 the frame shrinks continuously.
>
It doesn't here. Just in case, I tried a few different window managers
(IceWM, Fluxbox, Window Maker, ...) and the result was the same: the
scroll bar is displayed and hidden repeatedly, but the frame size doesn't
change (except of course by the few pixels that are used to display the
scroll bar).
>> But ISTM that telling Elisp programmers that such requests are
>> "committed" asynchronously, and that they can "commit" them immediately
>> by calling (redisplay t), should solve most similar problems.
>
> People changing the tab bar or the default font may be hardly aware of
> the fact that the toolkit stochastically resizes their frames behind
> their backs.
>
What would you suggest for this specific bug report? The OP hasn't
replied yet, so it's not yet know whether that advice solves their
problem, but don't you agree that calling (redisplay t) after calling
set-frame-size (and other similar functions) would in most cases help to
have the frame "in sync" with the code?
next prev parent reply other threads:[~2023-08-21 8:30 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-10 23:07 bug#65217: 29.1; set-frame-size gets confused and drops calls Ash
[not found] ` <handler.65217.B.169170885617684.ack@debbugs.gnu.org>
2023-08-10 23:16 ` Ash
2023-08-17 9:49 ` Eli Zaretskii
2023-08-17 16:44 ` martin rudalics
2023-08-18 1:13 ` Ash
2023-08-18 5:56 ` Eli Zaretskii
2023-08-18 6:04 ` Ash
2023-08-18 6:37 ` Eli Zaretskii
2023-08-18 7:23 ` Ash
2023-08-18 8:25 ` martin rudalics
2023-08-18 12:12 ` Eli Zaretskii
2023-08-18 8:34 ` Gregory Heytings
2023-08-18 12:14 ` Eli Zaretskii
2023-08-18 12:26 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-19 8:04 ` martin rudalics
2023-08-19 10:18 ` Gregory Heytings
2023-08-20 6:32 ` martin rudalics
2023-08-20 7:55 ` Gregory Heytings
2023-08-21 6:19 ` martin rudalics
2023-08-21 8:30 ` Gregory Heytings [this message]
2023-08-21 13:39 ` martin rudalics
2023-08-21 14:12 ` Gregory Heytings
2023-08-21 17:31 ` martin rudalics
2023-08-21 18:26 ` Gregory Heytings
2023-08-22 8:53 ` martin rudalics
2023-08-18 13:26 ` Gregory Heytings
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=77daee02cfc4d796b885@heytings.org \
--to=gregory@heytings.org \
--cc=65217@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=ext0l@catgirl.ai \
--cc=rudalics@gmx.at \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.