From: Eli Zaretskii <eliz@gnu.org>
To: martin rudalics <rudalics@gmx.at>,
"J. Scott Berg" <jsberg-bnl@outlook.com>
Cc: eric@ericabrahamsen.net, 44180@debbugs.gnu.org
Subject: bug#44180: 28.0.50; Emacs frames won't redisplay unless resized
Date: Sat, 24 Oct 2020 11:36:58 +0300 [thread overview]
Message-ID: <83tuukggut.fsf@gnu.org> (raw)
In-Reply-To: <7f32498b-1293-f1ee-5636-8ddd5bbff6c1@gmx.at> (message from martin rudalics on Sat, 24 Oct 2020 08:55:48 +0200)
> Cc: 44180@debbugs.gnu.org
> From: martin rudalics <rudalics@gmx.at>
> Date: Sat, 24 Oct 2020 08:55:48 +0200
>
> >> And if you revert that change, does the problem go away?
> >
> > Yes it does!
>
> Maybe we need an option for 2c0cd90083. Maybe we also should just
> wait. I'd expect a few more of such reports to drop in.
(Adding J. Scott to the addressees.)
What about ignoring these events only if the size is 1x1, which is
definitely bogus? Would that work in the VcXsrv case?
next prev parent reply other threads:[~2020-10-24 8:36 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-23 18:17 bug#44180: 28.0.50; Emacs frames won't redisplay unless resized Eric Abrahamsen
2020-10-23 18:25 ` Eli Zaretskii
2020-10-23 19:07 ` Eric Abrahamsen
2020-10-23 19:38 ` Eli Zaretskii
2020-10-23 21:07 ` Eric Abrahamsen
2020-10-24 6:55 ` martin rudalics
2020-10-24 8:36 ` Eli Zaretskii [this message]
2020-10-24 20:19 ` Eric Abrahamsen
2020-10-25 15:08 ` Eli Zaretskii
2020-10-25 16:01 ` Eric Abrahamsen
2020-10-25 16:16 ` Eli Zaretskii
2020-10-25 16:28 ` Eric Abrahamsen
2020-10-25 16:55 ` Eli Zaretskii
2020-10-25 18:26 ` Eric Abrahamsen
2020-10-26 18:24 ` martin rudalics
2020-10-26 19:51 ` Eric Abrahamsen
2020-10-27 9:08 ` martin rudalics
2020-10-27 18:11 ` Eric Abrahamsen
2020-10-27 18:45 ` Eli Zaretskii
2020-10-27 19:48 ` Eric Abrahamsen
2020-10-31 8:28 ` Eli Zaretskii
2020-11-06 1:52 ` Eric Abrahamsen
2022-04-24 14:08 ` Lars Ingebrigtsen
2022-04-24 15:26 ` Eric Abrahamsen
2022-04-24 15:27 ` Lars Ingebrigtsen
2020-10-25 16:26 ` Sascha Sadeghian
2020-10-25 16:57 ` Eli Zaretskii
2020-10-24 8:03 ` Eli Zaretskii
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=83tuukggut.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=44180@debbugs.gnu.org \
--cc=eric@ericabrahamsen.net \
--cc=jsberg-bnl@outlook.com \
--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).