From: "HS" <hugows@gmail.com>
Subject: Re: Changing control keys
Date: 18 Jan 2007 10:35:06 -0800 [thread overview]
Message-ID: <1169145306.635651.30860@v45g2000cwv.googlegroups.com> (raw)
In-Reply-To: <1169145123.458175.123740@51g2000cwl.googlegroups.com>
Most people do that by changing OS settings, isn't that a solution for
you?
H. escreveu:
> Unforuntately, left hand lacks the agility to press Ctrl and X without
> diverging from the home position, and the lab keyboards at my
> university lack a Ctrl key on the right.
>
> Therefore, my two questions:
> 1. I assume it's possible to change individual commands to use
> CAP-LOCKS instead of Ctrl, but could someone please remind me how this
> is done?
> 2. Is there a way to universally change all commands that use one
> control key to use another? (In this case, CTRL --> CAPS LOCK).
>
> Thanks!
next prev parent reply other threads:[~2007-01-18 18:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-18 18:32 Changing control keys H.
2007-01-18 18:35 ` HS [this message]
2007-01-18 19:53 ` Lennart Borgman (gmail)
[not found] ` <mailman.3266.1169150000.2155.help-gnu-emacs@gnu.org>
2007-01-18 20:14 ` HS
2007-01-18 21:06 ` David Hansen
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=1169145306.635651.30860@v45g2000cwv.googlegroups.com \
--to=hugows@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.
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).