unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: martin rudalics <rudalics@gmx.at>
Cc: 44180@debbugs.gnu.org
Subject: bug#44180: 28.0.50; Emacs frames won't redisplay unless resized
Date: Mon, 26 Oct 2020 12:51:37 -0700	[thread overview]
Message-ID: <87tuugn4ty.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <9ee49070-b0be-a775-18a2-3c9ee587210b@gmx.at> (martin rudalics's message of "Mon, 26 Oct 2020 19:24:21 +0100")

martin rudalics <rudalics@gmx.at> writes:

>> The problem is that switching focus between windows (frames) does not
>> update which window is "live". The most-recently created, or
>> most-recently resized, window is always the live one. If I switch focus
>> to one of the other frames, it doesn't update, and I need to move it
>> around somehow in order to make it live. Then the other frames go dead.
>>
>> 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.
>
> Do you get the corresponding focus events (whatever they are now) when
> you make another frame the fullscreen one?  If so, we should probably
> redraw the frame in that case.

I'm still not at the offending computer, but I think there's a high
likelihood of confusing myself with conflicting terminology here so,
just to be clear: this isn't proper fullscreening in the X11 sense. i3
also does that, but I hardly ever use it since the stacked layout is
close enough to full screen. In X11 terms I think all that's happening
is switching of focus between windows, it's just that i3's layout means
that the unfocused windows are always completely obscured. For some
reason Emacs now thinks that a window being obscured means that it's now
an icon. Switching focus back to that window does not un-iconify it.

Anyway, more later in the day...





  reply	other threads:[~2020-10-26 19:51 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 [this message]
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=87tuugn4ty.fsf@ericabrahamsen.net \
    --to=eric@ericabrahamsen.net \
    --cc=44180@debbugs.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).