unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: 44180@debbugs.gnu.org
Subject: bug#44180: 28.0.50; Emacs frames won't redisplay unless resized
Date: Sun, 25 Oct 2020 18:55:14 +0200	[thread overview]
Message-ID: <83pn56fdot.fsf@gnu.org> (raw)
In-Reply-To: <87zh4anucm.fsf@ericabrahamsen.net> (message from Eric Abrahamsen on Sun, 25 Oct 2020 09:28:09 -0700)

> From: Eric Abrahamsen <eric@ericabrahamsen.net>
> Cc: 44180@debbugs.gnu.org
> Date: Sun, 25 Oct 2020 09:28:09 -0700
> 
> >> Before the breakage, it's possible that the non-visible frames were not
> >> updated while they remained invisible, and I simply never knew because
> >> I couldn't see them. Now they stay un-updated until I manipulate the
> >> size of the window somehow.
> >
> > That seems to suggest that we don't trigger expose_frame calls anymore
> > for the frames that become un-fontified?
> 
> I wouldn't know, but that certainly sounds likely. I'd be happy to try
> contacting someone at i3, if that would be helpful, or to try fiddling
> with the display code.

What would help is if you put a breakpoint at expose_frame, and see
how it is called when the changes made by the offending commit are
reverted.  Please show which X event triggers that and with what
parameters.  Then do the same with the offending changes in place, and
try to figure out why the expose event doesn't get triggered.

Armed with that info, we could try finding a way of having the cake
and eating it, too.

TIA





  reply	other threads:[~2020-10-25 16:55 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
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 [this message]
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=83pn56fdot.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=44180@debbugs.gnu.org \
    --cc=eric@ericabrahamsen.net \
    /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).