From: Miles Bader <miles@gnu.org>
To: "Patishnock\, Timothy Mitchell" <patis1tm@cmich.edu>
Cc: emacs-devel@gnu.org
Subject: Re: GNU Emacs Custom Mechanical Keyboard Keycaps
Date: Sat, 23 Jun 2012 11:17:16 +0900 [thread overview]
Message-ID: <8762aiai1f.fsf@catnip.gol.com> (raw)
In-Reply-To: <1109857539.2058401.1340407813873.JavaMail.root@cmu-mailstore04> (Timothy Mitchell Patishnock's message of "Fri, 22 Jun 2012 19:30:13 -0400 (EDT)")
"Patishnock, Timothy Mitchell" <patis1tm@cmich.edu> writes:
> Which keys would you edit (space permitting on such a small surface) to
> indicate GNU Emacs functionality?
>
> I'm thinking about editing the <alt> key to read <META> on top and alt
> in italics below it. Also, the F10 key would read Emacs Menu underneath
> the F10 label.
I presume it'll have the control key in the right place, to the left
of the "a" key (that's priority number one with an Emacs keyboard).
How many additional modifier keys do you have (even my small HHKB has
two on either side of the spacebar, so I guess four total)? Besides a
"Meta-" key, you could have dedicated "Super-" and "Hyper-" keys...
[Getting those through the software stack is another issue of course;
presumably just a Small Matter of Programming... :]
-miles
--
What the fuck do white people have to be blue about!? Banana Republic ran
out of Khakis? The Espresso Machine is jammed? Hootie and The Blowfish
are breaking up??! Shit, white people oughtta understand, their job is to
GIVE people the blues, not to get them! -- George Carlin
next prev parent reply other threads:[~2012-06-23 2:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4FCFFB29.7060406@cmich.edu>
2012-06-22 23:30 ` GNU Emacs Custom Mechanical Keyboard Keycaps Patishnock, Timothy Mitchell
2012-06-23 1:49 ` Stefan Monnier
2012-06-23 2:17 ` Miles Bader [this message]
2012-06-23 3:25 ` Timothy Patishnock
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=8762aiai1f.fsf@catnip.gol.com \
--to=miles@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=patis1tm@cmich.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).