unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: martin rudalics <rudalics@gmx.at>
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: Tue, 27 Oct 2020 10:08:18 +0100	[thread overview]
Message-ID: <f9caf206-5eff-9373-e892-32d11eb39f86@gmx.at> (raw)
In-Reply-To: <87tuugn4ty.fsf@ericabrahamsen.net>

 >> 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.

I didn't expect it to be but thanks for confirming.

 > 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.

Always keep in mind that Emacs has no idea about whether and how a
window has been iconified or focused.  It just waits for the
corresponding information from the window manager, believes what the
latter tells and acts (redrawing a frame, for example) accordingly.

 > Anyway, more later in the day...

martin





  reply	other threads:[~2020-10-27  9:08 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 [this message]
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=f9caf206-5eff-9373-e892-32d11eb39f86@gmx.at \
    --to=rudalics@gmx.at \
    --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).