From: Po Lu <luangruo@yahoo.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>, emacs-devel@gnu.org
Subject: Re: Making `xwidget-event' a special event
Date: Fri, 19 Nov 2021 21:21:39 +0800 [thread overview]
Message-ID: <87v90ol1r0.fsf@yahoo.com> (raw)
In-Reply-To: <83fsrsuvt1.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 19 Nov 2021 15:19:54 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
> They are documented in "Special Events" in the ELisp manual. Maybe
> Stefan could add to that if the manual isn't comprehensive enough.
They seem fine, so if Stefan doesn't have anything to add I'll make the
change. Thanks.
prev parent reply other threads:[~2021-11-19 13:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87wnl4mjd4.fsf.ref@yahoo.com>
2021-11-19 12:15 ` Making `xwidget-event' a special event Po Lu
2021-11-19 12:47 ` Eli Zaretskii
2021-11-19 13:06 ` Po Lu
2021-11-19 13:19 ` Eli Zaretskii
2021-11-19 13:21 ` 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=87v90ol1r0.fsf@yahoo.com \
--to=luangruo@yahoo.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--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).