From: Eli Zaretskii <eliz@gnu.org>
To: Po Lu <luangruo@yahoo.com>
Cc: larsi@gnus.org, monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: Touchscreen support
Date: Mon, 20 Dec 2021 17:18:19 +0200 [thread overview]
Message-ID: <831r272tl0.fsf@gnu.org> (raw)
In-Reply-To: <87r1a85c5i.fsf@yahoo.com> (message from Po Lu on Mon, 20 Dec 2021 08:54:17 +0800)
> From: Po Lu <luangruo@yahoo.com>
> Cc: larsi@gnus.org, monnier@iro.umontreal.ca, emacs-devel@gnu.org
> Date: Mon, 20 Dec 2021 08:54:17 +0800
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> From: Po Lu <luangruo@yahoo.com>
> >> Cc: larsi@gnus.org, monnier@iro.umontreal.ca, emacs-devel@gnu.org
> >> Date: Sun, 19 Dec 2021 19:42:31 +0800
> >>
> >> > I'm not opposed to having parts of this in Lisp, but I do want to see
> >> > the events placed in the normal Emacs input queue, which probably
> >> > means that Lisp will be called from C. Not sure if such design will
> >> > make sense in practice, though. But OTOH, having events coming in
> >> > from another source, not through the input queue read by
> >> > read_socket_hook, is a complication I'd very much prefer to avoid (if
> >> > it's even feasible).
> >>
> >> We could have an API that allows Lisp to push some kinds of input events
> >> to that queue, which is then read by the various read_socket_hooks.
>
> > How would the low-level events, from which you want to construct
> > higher-level events, get to Lisp in the first place?
>
> Through the usual event system (though probably as special events in
> special-event-map).
So the events from X will be delivered via read_socket_hook, then the
code which reads these events will call Lisp, and then it will turn
around and feed the synthetic events it produces back into the input
queue? That's exactly what I prefer to avoid, since there's no way in
the world you will be able to pretend that the synthetic events were
delivered in the same place as the real ones: some additional events
could have arrived meanwhile.
next prev parent reply other threads:[~2021-12-20 15:18 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87czlxkntg.fsf.ref@yahoo.com>
2021-12-16 7:31 ` Touchscreen support Po Lu via Emacs development discussions.
2021-12-16 7:58 ` Lars Ingebrigtsen
2021-12-16 8:02 ` Po Lu
2021-12-17 6:19 ` Po Lu
2021-12-17 7:17 ` Lars Ingebrigtsen
2021-12-17 12:29 ` Stefan Monnier
2021-12-17 12:36 ` Po Lu
2021-12-17 13:18 ` Stefan Monnier
2021-12-17 13:48 ` Po Lu
2021-12-17 16:00 ` Stefan Monnier
2021-12-18 0:02 ` Po Lu
2021-12-18 16:22 ` Stefan Monnier
2021-12-18 19:12 ` Stefan Monnier
2021-12-18 4:41 ` Richard Stallman
2021-12-18 4:53 ` Po Lu
2021-12-20 4:42 ` Richard Stallman
2021-12-20 4:59 ` Po Lu
2021-12-21 4:15 ` Richard Stallman
2021-12-21 4:35 ` Po Lu
2021-12-22 4:16 ` Richard Stallman
2021-12-22 4:39 ` Po Lu
2021-12-23 3:43 ` Richard Stallman
2021-12-23 4:46 ` Po Lu
2021-12-26 3:57 ` Richard Stallman
2021-12-26 5:02 ` Po Lu
2021-12-27 4:14 ` Richard Stallman
2021-12-27 6:05 ` Stefan Monnier
2021-12-28 4:19 ` Richard Stallman
2022-01-15 0:17 ` chad
2022-01-15 0:48 ` Po Lu
2022-01-16 5:07 ` Richard Stallman
2022-01-16 5:35 ` Po Lu
2021-12-18 7:48 ` Lars Ingebrigtsen
2021-12-18 14:46 ` Eli Zaretskii
2021-12-19 0:24 ` Po Lu
2021-12-19 8:14 ` Eli Zaretskii
2021-12-19 9:24 ` Po Lu
2021-12-19 9:32 ` Eli Zaretskii
2021-12-19 9:38 ` Po Lu
2021-12-19 11:31 ` Eli Zaretskii
2021-12-19 11:42 ` Po Lu
2021-12-19 17:58 ` Eli Zaretskii
2021-12-20 0:54 ` Po Lu
2021-12-20 15:18 ` Eli Zaretskii [this message]
2021-12-21 1:08 ` Po Lu
2021-12-21 12:11 ` Eli Zaretskii
2021-12-21 12:21 ` Po Lu
2021-12-21 14:17 ` Eli Zaretskii
2021-12-19 18:26 ` [External] : " Drew Adams
2021-12-20 4:42 ` Richard Stallman
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=831r272tl0.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.org \
--cc=luangruo@yahoo.com \
--cc=monnier@iro.umontreal.ca \
/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).