From: Po Lu <luangruo@yahoo.com>
To: "Qiantan Hong" <qthong@stanford.edu>
Cc: "emacs-devel@gnu.org" <emacs-devel@gnu.org>,"Lars Ingebrigtsen"
<larsi@gnus.org>
Subject: Re: Suggestion: Remove direct keyboard handling for active elements fr
Date: Sat, 15 Oct 2022 09:47:35 +0800 [thread overview]
Message-ID: <874jw5rh6w.fsf@yahoo.com> (raw)
In-Reply-To: Your message of Fri, 14 Oct 2022 21:58:07 +0000 <95D035E8-30B4-46D3-AC0C-8C9A9F706DF7@stanford.edu>
In general, not a bad idea. However, the NS xwidget implementation does
not support passing through input events at all (this is a new feature
in Emacs 29), so that will have to be implemented first.
prev parent reply other threads:[~2022-10-15 1:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-14 21:58 Suggestion: Remove direct keyboard handling for active elements from NS Webkit Xwidgets Qiantan Hong
2022-10-15 1:47 ` Po Lu [this message]
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=874jw5rh6w.fsf@yahoo.com \
--to=luangruo@yahoo.com \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.org \
--cc=qthong@stanford.edu \
/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).