From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Po Lu <luangruo@yahoo.com>
Cc: emacs-devel@gnu.org
Subject: Re: master 3b41141708: Expose the name of an event's input device to Lisp
Date: Sat, 09 Apr 2022 10:20:06 -0400 [thread overview]
Message-ID: <jwvo81a2vlr.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87pmlql6mj.fsf@yahoo.com> (Po Lu's message of "Sat, 09 Apr 2022 21:37:56 +0800")
>> But I agree that the current representation of events is problematic.
>> We should make it more regular and self-descriptive, either based on an
>> alist as above or have every event come with some kind of "class" which
>> then describes the name&position of every accompanying data.
> Unfortunately, our current representation is basically set in stone.
To some extent, yes, but we can try and design the new representation to
be compatible with the old one. E.g. the "class" could be obtained via:
(defun event-class (e)
(if (consp e)
(get (event-basic-type e) 'event-class)
character-event-class))
> There is too much Lisp out there that relies on the current form of Lisp
> events, and simply finding all that code will be a serious chore.
Yup, that's why we have to introduce the new API in a way that's
backward compatible.
> Maybe we could introduce a new representation of event in addition to
> the current form, with a its own interactive form and read-event, that
> represents events as some better data structure?
Here, I'd side with Eli and say that the resulting code churn wojuld be
more trouble than it's worth.
[ Most of that work has already been done in the context of
XEmacs, but I doubt we'd be able to make use of it, sadly. ]
Stefan
next prev parent reply other threads:[~2022-04-09 14:20 UTC|newest]
Thread overview: 86+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <164933858147.29834.15050766441005536059@vcs2.savannah.gnu.org>
[not found] ` <20220407133623.9C209C009A8@vcs2.savannah.gnu.org>
2022-04-07 14:05 ` master 3b41141708: Expose the name of an event's input device to Lisp Stefan Monnier
2022-04-07 23:31 ` Po Lu
2022-04-07 23:41 ` Stefan Monnier
2022-04-08 0:07 ` Po Lu
2022-04-08 6:02 ` Eli Zaretskii
2022-04-08 6:08 ` Po Lu
2022-04-08 6:26 ` Eli Zaretskii
2022-04-08 7:36 ` Po Lu
2022-04-08 11:12 ` Eli Zaretskii
2022-04-08 11:31 ` Po Lu
2022-04-08 12:12 ` Eli Zaretskii
2022-04-08 12:35 ` Po Lu
2022-04-09 6:48 ` Eli Zaretskii
2022-04-09 9:06 ` Po Lu
2022-04-09 9:09 ` Lars Ingebrigtsen
2022-04-09 9:30 ` Eli Zaretskii
2022-04-09 10:03 ` Po Lu
2022-04-09 11:03 ` Eli Zaretskii
2022-04-09 11:44 ` Po Lu
2022-04-09 14:04 ` Eli Zaretskii
2022-04-09 16:33 ` Stefan Monnier
2022-04-09 16:41 ` Lars Ingebrigtsen
2022-04-09 17:06 ` Eli Zaretskii
2022-04-09 17:16 ` Eli Zaretskii
2022-04-09 17:52 ` Brian Cully
2022-04-09 19:18 ` Eli Zaretskii
2022-04-10 0:54 ` Po Lu
2022-04-10 1:46 ` Brian Cully
2022-04-10 2:11 ` Po Lu
2022-04-10 2:45 ` Brian Cully
2022-04-10 3:30 ` Po Lu
2022-04-10 0:37 ` Po Lu
2022-04-10 5:49 ` Eli Zaretskii
2022-04-10 6:09 ` Po Lu
2022-04-10 6:44 ` Eli Zaretskii
2022-04-10 7:31 ` Po Lu
2022-04-10 8:28 ` Eli Zaretskii
2022-04-10 8:50 ` Po Lu
2022-04-10 9:17 ` Eli Zaretskii
2022-04-10 9:25 ` Po Lu
2022-04-10 11:15 ` Po Lu
2022-04-10 15:16 ` Stefan Monnier
2022-04-11 1:02 ` Po Lu
2022-04-10 11:46 ` Lars Ingebrigtsen
2022-04-10 11:41 ` Lars Ingebrigtsen
2022-04-10 0:48 ` Po Lu
2022-04-10 6:04 ` Eli Zaretskii
2022-04-10 6:17 ` Po Lu
2022-04-10 6:49 ` Eli Zaretskii
2022-04-10 7:01 ` Po Lu
2022-04-10 8:24 ` Eli Zaretskii
2022-04-10 8:42 ` Po Lu
2022-04-10 9:13 ` Eli Zaretskii
2022-04-10 12:51 ` Brian Cully
2022-04-10 13:21 ` Po Lu
2022-04-10 18:08 ` Brian Cully
2022-04-11 0:58 ` Po Lu
2022-04-11 1:08 ` Brian Cully
2022-04-11 2:00 ` Po Lu
2022-04-11 2:03 ` Po Lu
2022-04-11 2:21 ` Brian Cully
2022-04-11 3:12 ` Po Lu
2022-04-11 4:11 ` Brian Cully
2022-04-11 5:20 ` Po Lu
2022-04-11 11:33 ` Brian Cully
2022-04-11 14:09 ` Po Lu
2022-04-11 16:26 ` Brian Cully
2022-04-11 10:10 ` Lars Ingebrigtsen
2022-04-10 12:44 ` Brian Cully
2022-04-10 13:14 ` Po Lu
2022-04-08 14:27 ` Stefan Monnier
2022-04-09 0:24 ` Po Lu
2022-04-09 2:52 ` Stefan Monnier
2022-04-09 3:17 ` Po Lu
2022-04-09 13:31 ` Stefan Monnier
2022-04-09 13:37 ` Po Lu
2022-04-09 14:20 ` Stefan Monnier [this message]
2022-04-10 0:58 ` Po Lu
2022-04-09 14:31 ` Eli Zaretskii
2022-04-10 0:56 ` Po Lu
2022-04-10 6:11 ` Eli Zaretskii
2022-04-10 6:23 ` Po Lu
2022-04-10 6:52 ` Eli Zaretskii
2022-04-10 7:37 ` Po Lu
2022-04-10 8:12 ` Eli Zaretskii
2022-04-09 6:22 ` Eli Zaretskii
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=jwvo81a2vlr.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.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.