From: Ash <ext0l@catgirl.ai>
To: Eli Zaretskii <eliz@gnu.org>
Cc: rudalics@gmx.at, 65217@debbugs.gnu.org
Subject: bug#65217: 29.1; set-frame-size gets confused and drops calls
Date: Fri, 18 Aug 2023 00:23:56 -0700 [thread overview]
Message-ID: <55cd7e5c-3685-231a-77bb-16d4785ed9f0@catgirl.ai> (raw)
In-Reply-To: <83h6ow500n.fsf@gnu.org>
On 8/17/23 23:37, Eli Zaretskii wrote:
>> Date: Thu, 17 Aug 2023 23:04:06 -0700
>> Cc: rudalics@gmx.at, 65217@debbugs.gnu.org
>> From: Ash <ext0l@catgirl.ai>
>>
>> On 8/17/23 22:56, Eli Zaretskii wrote:
>>
>> Can we close this bug, or is there anything left to do here?
>>
>> IMO the fact that a set-frame-size call can fail to have an effect is absolutely a bug.
> I disagree. It is a consequence of the fact that the actual resizing
> is performed by the window manager, and that Emacs must wait for the
> window-system response event to perform the resize correctly. Lisp
> programs that perform several such operations in a row must inject
> short wait periods to allow for the processing of the window-system
> events. That's what Martin meant by saying that using sit-for solves
> the problems.
>
> So this isn't a bug, but a limitation caused by the way Emacs's
> interaction with the GUI systems is designed. If by "bug" you mean
> that design, then it is pointless to keep such "bugs" open, since no
> one is working on redesigning that aspect of Emacs, nor intends to do
> so any time soon.
I think if making this specific case work would require a substantial
change then it's fine closing this out. But then I think there should be
documentation that this can happen somewhere (in the general emacs
documentation on frames, maybe with a link from the set-frame-size docs).
next prev parent reply other threads:[~2023-08-18 7:23 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 [this message]
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
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
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=55cd7e5c-3685-231a-77bb-16d4785ed9f0@catgirl.ai \
--to=ext0l@catgirl.ai \
--cc=65217@debbugs.gnu.org \
--cc=eliz@gnu.org \
--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 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).