From: martin rudalics <rudalics@gmx.at>
To: Gregory Heytings <gregory@heytings.org>
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: Sun, 20 Aug 2023 08:32:02 +0200 [thread overview]
Message-ID: <93b5b958-fc04-9ab4-69cd-2ffaa95fb525@gmx.at> (raw)
In-Reply-To: <387ee04aa99416f015d1@heytings.org>
> I'm not sure yet, but after thinking a bit more about this, ATM my
> conclusion is that adding a sentence in the docstings of set-frame-*
> and modify-frame-parameters, suggesting to use (redisplay t) after
> these functions, would be enough.
Not really, I think. With emacs -Q try
(let ((i 100))
(while (> i 0)
(scroll-bar-mode -1)
(scroll-bar-mode 1)
(sit-for 0.1)
(setq i (1- i))))
martin
next prev parent reply other threads:[~2023-08-20 6:32 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 [this message]
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=93b5b958-fc04-9ab4-69cd-2ffaa95fb525@gmx.at \
--to=rudalics@gmx.at \
--cc=65217@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=ext0l@catgirl.ai \
--cc=gregory@heytings.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).