all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Jacky Li <drsl@drshapeless.com>, 58245@debbugs.gnu.org
Subject: bug#58245: 29.0.50; other-frame is broken in EXWM
Date: Sun, 02 Oct 2022 22:24:52 +0800	[thread overview]
Message-ID: <87v8p22thn.fsf@yahoo.com> (raw)
In-Reply-To: <87mtaecs6d.fsf@gnus.org> (Lars Ingebrigtsen's message of "Sun, 02 Oct 2022 14:43:06 +0200")

Lars Ingebrigtsen <larsi@gnus.org> writes:

>> 3924fbd025 is not buggy; EXWM enables support for _NET_ACTIVE_WINDOW,
>> which Emacs expects to be implemented correctly:
>
> It's a regression, and should be fixed on the Emacs side.

The previous code was causing problems for me, namely C-x 5 o not
working on the GNOME Flashback session (which I have been trying to move
to, large memory leaks upon taking screenshots in GNOME Shell being the
last straw.)

This is because the previous code had two problems: SetInputFocus called
with CurrentTime changed the last-focus-change-time to the current X
server time, which is later than the time specified in the
_NET_ACTIVE_WINDOW message.  So, when Metacity tried to set the input
focus in response to the _NET_ACTIVE_WINDOW message, it failed, as the
timestamp specified in the _NET_ACTIVE_WINDOW became out of date.

As a result, the workspace of the frame being switched to was not made
current by the window manager.

We cannot possibly make Emacs stop working with a correctly written and
widely used window manager in favor of broken window managers,
especially those that mess with internal details of Emacs' X
communication.  Emacs does not guarantee that it will always interact
with the X server in the same fashion, and any external program making
assumptions there is in uncharted territory.  The problem should be
fixed in EXWM; in the meantime, Jack can do:

  (setq x-no-window-manager t)

which will make Emacs skip communicating with the "window manager"
(which is actually Emacs itself; I'm surprised that doesn't lead to
hangs elsewhere.)





  reply	other threads:[~2022-10-02 14:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-02  4:11 bug#58245: 29.0.50; other-frame is broken in EXWM Jacky Li via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-02 12:31 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-02 12:43   ` Lars Ingebrigtsen
2022-10-02 14:24     ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-11-04 23:23       ` Adrián Medraño Calvo
2022-11-12 21:11         ` bug#58245: bug#58438: 29.0.50; EXWM focus lost Stefan Kangas

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87v8p22thn.fsf@yahoo.com \
    --to=bug-gnu-emacs@gnu.org \
    --cc=58245@debbugs.gnu.org \
    --cc=drsl@drshapeless.com \
    --cc=larsi@gnus.org \
    --cc=luangruo@yahoo.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.