unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Sascha Sadeghian <sadeghian@acm.org>
Cc: eric@ericabrahamsen.net, 44180@debbugs.gnu.org
Subject: bug#44180: 28.0.50; Emacs frames won't redisplay unless resized
Date: Sun, 25 Oct 2020 18:57:38 +0200	[thread overview]
Message-ID: <83o8kqfdkt.fsf@gnu.org> (raw)
In-Reply-To: <20201025162618.GA46534@gamma.sadeghian.org> (message from Sascha Sadeghian on Sun, 25 Oct 2020 17:26:18 +0100)

> Date: Sun, 25 Oct 2020 17:26:18 +0100
> From: Sascha Sadeghian <sadeghian@acm.org>
> Cc: Eric Abrahamsen <eric@ericabrahamsen.net>, 44180@debbugs.gnu.org
> 
> Let’s say we start with an Emacs GTK window and an xterm window side by
> side, so that each has 50% of the total screen width ("split" mode in
> i3). If I switch to "tabbed" mode now and select the Emacs tab, the
> Emacs frame is unresponsive, and its contents are not redrawn any more.
> 
> This didn’t happen before 2c0cd90083.
> 
> Here is a quick demo with emacs -Q:
> 
>   https://webterm.io/bug-gnu-emacs/44180-working.webm
>   https://webterm.io/bug-gnu-emacs/44180-broken.webm
> 
> The bug can be reproduced with a single frame.
> 
> The confusing part is probably that for this frozen frame, keyboard
> input is still working, so buffers can be edited, while the edits are
> only visible in other, non-frozen frames (for example, a second
> emacsclient frame showing the same buffers). The GTK menu and toolbar
> are also not affected.

This is actually not confusing at all, it is entirely expected.

> Hope this helps!

I've just explained to Eric which information would be helpful to make
some progress here.  If you can help collecting that information, it
will be really appreciated.

Thanks.





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