From: Alexander Klimov <alserkli@inbox.ru>
To: emacs-devel@gnu.org
Cc: chad <yandros@mit.edu>, Stefan Monnier <monnier@iro.umontreal.ca>
Subject: Re: Monitoring KeyRelease
Date: Sat, 7 Jul 2012 01:05:00 +0300 [thread overview]
Message-ID: <TheMailAgent.4b5f2c59@54bc90be> (raw)
In-Reply-To: <0A8301B6-E422-45F7-BBA3-04A2E812AE71@mit.edu>
On Fri, 6 Jul 2012, chad wrote:
> Have you tried this on a terminal? My understanding is that it just
> won't work on most terminals, but it's been a long time (~15 years)
> since I actually looked.
I have not tried, but you are right -- it will not work on terminal,
at least not on remote host, since such terminals do not provide an
analog of KeyRelease.
OTOH, there are many features in Emacs that do not work in every UI
(say, in-line images), but it does not make these features less useful
in situations where they do work.
> At the time, it seemed like letter-based modifiers were routinely
> unclean. There were some combinations that were workable, but they
> depended on the keyboard layout (basically, you take advantage of
> the qwerty pretzel-combos). The spacebar is a pretty solid
> potential modifier, because almost everyone hits it with their
> thumb, but there's some annoying IP in this area.
Probably the whole idea that modifier must be a separate key is an
atavism of the mechanical design: on a computer keyboard any key can
be potentially used as a modifier. The advantage is a reduction of RSI
since pressing a key in the home row is easier than pressing the
proper modifier.
--
Regards,
ASK
prev parent reply other threads:[~2012-07-06 22:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-05 17:25 Monitoring KeyRelease Alexander Klimov
2012-07-05 20:14 ` Stefan Monnier
2012-07-06 18:38 ` Alexander Klimov
2012-07-06 18:47 ` Andreas Schwab
2012-07-06 21:20 ` Alexander Klimov
2012-07-06 19:00 ` chad
2012-07-06 22:05 ` Alexander Klimov [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=TheMailAgent.4b5f2c59@54bc90be \
--to=alserkli@inbox.ru \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=yandros@mit.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).