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>, Eli Zaretskii <eliz@gnu.org>
Cc: 44180@debbugs.gnu.org
Subject: bug#44180: 28.0.50; Emacs frames won't redisplay unless resized
Date: Sat, 24 Oct 2020 08:55:48 +0200	[thread overview]
Message-ID: <7f32498b-1293-f1ee-5636-8ddd5bbff6c1@gmx.at> (raw)
In-Reply-To: <87lffw1wjv.fsf@ericabrahamsen.net>

I just meant that their 'visibility frame-parameter became 'icon. Their
 > "real" visibility is the same as always -- the two non-focused frames
 > are visible only as stacked title bars above the currently focused frame.

Can you please describe this in more detail.  As I understand it, your
initial frame looks as usual until you do C-x 5 2.  At that moment, the
initial frame becomes non-focused and appears as a stacked title bar
while the new frame becomes focused and appears as expected.  Is that
right?  Then how does the "fullscreen frames by default" fit into this
picture and how does a tiling manager use stacking?

 >>> I haven't changed anything in my window manager config, and the i3
 >>> package hasn't been updated since August. The only recent commit that
 >>> looks like it could be at all relevant is 2c0cd90083.
 >>
 >> 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.

martin





  reply	other threads:[~2020-10-24  6: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 [this message]
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
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=7f32498b-1293-f1ee-5636-8ddd5bbff6c1@gmx.at \
    --to=rudalics@gmx.at \
    --cc=44180@debbugs.gnu.org \
    --cc=eliz@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).