all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Adrián Medraño Calvo" <adrian@medranocalvo.com>
To: Po Lu <luangruo@yahoo.com>
Cc: Jacky Li <drsl@drshapeless.com>,
	58245@debbugs.gnu.org, Lars Ingebrigtsen <larsi@gnus.org>
Subject: bug#58245: 29.0.50; other-frame is broken in EXWM
Date: Sat, 5 Nov 2022 00:23:37 +0100	[thread overview]
Message-ID: <118EED5D-5178-4B36-B0C9-6439352602A0@medranocalvo.com> (raw)
In-Reply-To: <87v8p22thn.fsf@yahoo.com>

On 2. Oct 2022, at 16:24, Po Lu <luangruo@yahoo.com> wrote:
> 
> 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 problem should be fixed in EXWM

I agree, the problem should be fixed in EXWM: it implements _NET_ACTIVE_WINDOW incorrectly (or, assumed Emacs would take care of parts of it).  We are working on fixing it: https://github.com/ch11ng/exwm/pull/890, though it’s not enough.

I think this bug report can be closed.

Thank you both for your work on Emacs, and this time especially Po Lu for your help with EXWM.

Kind regards,
Adrián.




  reply	other threads:[~2022-11-04 23:23 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
2022-11-04 23:23       ` Adrián Medraño Calvo [this message]
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=118EED5D-5178-4B36-B0C9-6439352602A0@medranocalvo.com \
    --to=adrian@medranocalvo.com \
    --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.