unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: martin rudalics <rudalics@gmx.at>
To: Tom Gillespie <tgbugs@gmail.com>, Emacs developers <emacs-devel@gnu.org>
Subject: Re: [PATCH] Fix rendering issues on window managers without _NET_WM_STATE
Date: Sat, 15 May 2021 09:57:44 +0200	[thread overview]
Message-ID: <015406d8-35d0-b76a-bee9-f2cc0c3d286c@gmx.at> (raw)
In-Reply-To: <CA+G3_PMLyu8orBSDvVA9NO=v_oAAO4rH_mW+-Ky4Nfh9y0XYVQ@mail.gmail.com>

 >      This patch fixes a bug that occurs when running Emacs in a window
 > manager that does not set _NET_WM_STATE. The patch is simplest fix
 > that restores expected behavior for window managers that do not set
 > _NET_WM_STATE, but I have no idea whether there are other issues that
 > may be occurring.
 >
 > I'm guessing that there are also likely issues with other logic in the
 > MapNotify case that uses not_hidden for window managers that does not
 > set _NET_WM_STATE.
 >
 > Thus, the more complex solution, which I am not knowledgeable enough
 > to implement correctly, is to fix x_get_current_wm_state so that it
 > works on window managers that do not set _NET_WM_STATE.
 >
 > I am unfamiliar with this section of the code, so my explanation may
 > be off and a sanity check would be appreciated. Best,

Thanks.  This explains why our MapNotify code was not able to handle
visibility correctly with some WMs.  Actually, this also means that we
should get rid of x_get_current_wm_state because it apparently fails in
too many cases.

Unfortunately, reverting parts of 483c5e953c1 as in your patch will only
reintroduce the bug 483c5e953c1 was trying to fix.  I meanwhile checked
in a different solution based on handling VisibilityNotify.  Please try
with latest master and tell us whether the problem still exists.

Thank you, martin



  parent reply	other threads:[~2021-05-15  7:57 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-15  1:55 [PATCH] Fix rendering issues on window managers without _NET_WM_STATE Tom Gillespie
2021-05-15  7:09 ` Omar Polo
2021-05-16  8:30   ` martin rudalics
2021-05-16 13:45     ` Omar Polo
2021-05-16 14:51       ` martin rudalics
2021-05-16 16:14         ` Omar Polo
2021-05-18  3:45           ` Tom Gillespie
2021-05-18  8:01             ` martin rudalics
2021-05-18 13:03               ` Basil L. Contovounesios
2021-05-18 13:31                 ` martin rudalics
2021-05-18 14:43                   ` Basil L. Contovounesios
2021-05-15  7:57 ` martin rudalics [this message]
2021-05-15 17:40   ` Tom Gillespie
2021-05-16  8:30     ` martin rudalics

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=015406d8-35d0-b76a-bee9-f2cc0c3d286c@gmx.at \
    --to=rudalics@gmx.at \
    --cc=emacs-devel@gnu.org \
    --cc=tgbugs@gmail.com \
    /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).