From: Theodor Thornhill via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Po Lu <luangruo@yahoo.com>
Cc: Lars Ingebrigtsen <larsi@gnus.org>,
53062@debbugs.gnu.org, Eli Zaretskii <eliz@gnu.org>
Subject: bug#53062: 29.0.50; Inserting charger causes keyboard event <dead-circumflex>
Date: Fri, 14 Jan 2022 13:53:34 +0100 [thread overview]
Message-ID: <87wnj2fpgx.fsf@thornhill.no> (raw)
In-Reply-To: <87lezifqkb.fsf@yahoo.com>
Po Lu <luangruo@yahoo.com> writes:
> Theodor Thornhill <theo@thornhill.no> writes:
>
>> I tried to reproduce this again, but now I only get a message telling me
>> it's not running under X when using --with-pgtk. clean configure works
>> fine. I use exwm. I'll look into reproducing with the commit I reported
>> the bug with.
>
> Thanks, but I don't understand what message you allude to, and where
> it's from. Could you show the error message?
>
This code resides in exwm.el, and is the one messaging the error
(when (not (eq 'x (framep frame)))
(message "[EXWM] Not running under X environment")
(cl-return-from exwm-init))
This seems to be because (framep frame) returns 'pgtk, and not 'x. So
exwm cannot run under 'pgtk, it seems. Not sure if that is _only_ a bug
in exwm, or maybe should also be addressed in pgtk?
>> Side note: is it expected that exwm error when running --with-pgtk under
>> X? The only difference in setup is that option set or not. Exwm is run
>> with startx, so I assume we are in X.
>
> Yes. You should not use the PGTK build under X, it is much worse than
> the regular X build in every aspect.
>
Right, gotcha
next prev parent reply other threads:[~2022-01-14 12:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-06 21:48 bug#53062: 29.0.50; Inserting charger causes keyboard event <dead-circumflex> Theodor Thornhill via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-07 6:48 ` Eli Zaretskii
2022-01-07 7:27 ` Theodor Thornhill via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-10 21:20 ` Theodor Thornhill via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-14 8:09 ` Lars Ingebrigtsen
2022-01-14 9:33 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-14 12:18 ` Theodor Thornhill via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-14 12:29 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-14 12:53 ` Theodor Thornhill via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-01-14 13:06 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-14 13:12 ` Theodor Thornhill via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=87wnj2fpgx.fsf@thornhill.no \
--to=bug-gnu-emacs@gnu.org \
--cc=53062@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=larsi@gnus.org \
--cc=luangruo@yahoo.com \
--cc=theo@thornhill.no \
/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.