From: Doug Alcorn <lathinet@gmail.com>
Subject: Modifier keys in Carbon Emacs
Date: Thu, 16 Sep 2004 17:19:58 -0400 [thread overview]
Message-ID: <8f56a06e04091614196b79d302@mail.gmail.com> (raw)
I had complained briefly in another thread about certain non-mac-ness
of the carbon port of emacs. I think I can boil all of it down to how
modifier keys are handled. I know about mac-command-key-is-meta and
mac-pass-*-to-system. What I can't decide is how to best use them.
On the one hand (as a new mac user) I'm trying to get used to all the
Cmd-X keyboard shortcuts. On the other hand (as a recent Linux user)
I'm used to Alt being Meta and being immediately next to the space
bar. Leaving mac-command-key-is-meta set as t means that I won't be
able to use Cmd-tab to switch apps. If I set
mac-pass-command-to-system it means emacs will have a much reduced
keymapping.
I guess ideally I'd like to set mac-command-key-is-meta to nil so that
Alt/Option is Meta; however, I'd also like to have some new variable
mac-command-key-is-hyper that I can set t and then
mac-pass-command-key-to-system t. That way I can have all my
"standard" emacs keys mapped to meta and also use Cmd to map other
commands. For instance I could map H-` to other-frame and H-m to
iconify-frame among other things.
Anyway, I'd appreciate advice on the best way to handle modifier keys
so that I can keep both standard emacs bindings and standard mac
bindings.
--
(__) Doug Alcorn - Unix/Linux/Web Developing
oo / mailto:lathinet@gmail.com http://www.lathi.net
|_/
next reply other threads:[~2004-09-16 21:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-16 21:19 Doug Alcorn [this message]
2004-09-16 23:07 ` Modifier keys in Carbon Emacs Steven Tamm
2004-09-17 13:52 ` Doug Alcorn
2004-09-17 14:16 ` Doug Alcorn
2004-09-17 16:21 ` Doug Alcorn
2004-09-18 8:05 ` YAMAMOTO Mitsuharu
2004-09-18 9:55 ` Kai Grossjohann
2004-09-18 11:45 ` Gian Uberto Lauri
2004-09-17 0:20 ` Denis Bueno
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=8f56a06e04091614196b79d302@mail.gmail.com \
--to=lathinet@gmail.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 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).