From: Richard Stallman <rms@gnu.org>
To: "Mattias Engdegård" <mattiase@acm.org>
Cc: alan@idiocy.org, 38296@debbugs.gnu.org
Subject: bug#38296: Allow Option key to be modifier for non-char key and mouse events
Date: Wed, 27 Nov 2019 01:40:49 -0500 [thread overview]
Message-ID: <E1iZr0L-0007X9-7S@fencepost.gnu.org> (raw)
In-Reply-To: <C1305DC9-8042-4A23-8D7B-DE2E40CE2CA0@acm.org> (message from Mattias Engdegård on Mon, 25 Nov 2019 20:15:31 +0100)
[[[ To any NSA and FBI agents reading my email: please consider ]]]
[[[ whether defending the US Constitution against all enemies, ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]
> Looking at Mitsuharu Yamamoto's Mac port made me change my mind: it solves the problem by allowing the variables to have values on the form (:ordinary SYMBOL :function SYMBOL :mouse SYMBOL), defining each modifier key separately for ordinary keys, function keys and mouse events.
I'd like to understand what that feature does, but I can't tell from
that text. Does it come with any documentation? If so, coulod you
please show it?
Also, are you proposing we implement this for ALL platforms (that
would be clean and simple, in principle)? Or just SOME platforms?
--
Dr Richard Stallman
Founder, Free Software Foundation (https://gnu.org, https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)
next prev parent reply other threads:[~2019-11-27 6:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-20 10:55 bug#38296: Allow Option key to be modifier for non-char key and mouse events Mattias Engdegård
2019-11-21 18:39 ` Mattias Engdegård
2019-11-21 21:12 ` Alan Third
2019-11-22 20:01 ` Mattias Engdegård
2019-11-25 19:15 ` Mattias Engdegård
2019-11-26 20:33 ` Alan Third
2019-11-26 21:36 ` Mattias Engdegård
2019-11-26 22:03 ` Alan Third
2019-11-27 10:50 ` Mattias Engdegård
2019-11-27 4:51 ` Eli Zaretskii
2019-11-27 6:40 ` Richard Stallman [this message]
2019-11-27 10:45 ` Mattias Engdegård
2019-11-28 4:17 ` 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=E1iZr0L-0007X9-7S@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=38296@debbugs.gnu.org \
--cc=alan@idiocy.org \
--cc=mattiase@acm.org \
/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).