From: "Daniel B." <dsb@smart.net>
Cc: help-gnu-emacs@gnu.org
Subject: Re: C-f, C-b, C-n and C-p or right, left, down, up?
Date: Wed, 01 Oct 2003 12:43:09 -0400 [thread overview]
Message-ID: <3F7B041D.C0048AB@smart.net> (raw)
In-Reply-To: 1c58a7c3.0310010003.78c0fa00@posting.google.com
Barman Brakjoller wrote:
>
> >From the Emacs tutorial (C-h t):
>
> "... We recommend learning C-b, C-f, C-n and C-p for three
> reasons. First, they work on all kinds of terminals. Second, once
> you gain practice at using Emacs, you will find that typing these
> Control
> characters is faster than typing the arrow keys ..."
>
> Is it worth it?
Yes, but reconfigure your keyboard so that the Caps Lock key functions
as the control key. (I'm assuming you're using a PC-style keyboard.)
Emacs control-character sequences were designed when the standard place
for the control key was just to the left of where the A key is (in the
US layout).
Unfortunately, IBM put the Caps Lock key to the left of the A key, and
pushed the Control key down into a corner where it's hard to reach and
is extremely inconvenient for many Emacs control characters.
If you reconfigure your keyboard, you'll understand how Emacs control
characters were meant to be used. If you don't, you'll wonder how on
earth anyone can think control-character sequences are faster.
If you're running Emacs on Linux under X11 (e.g., GNOME, KDE), you can
reconfigure your control and caps-lock keys in X11's configuration file.
If you're running Emacs on MS Windows, see NTEmac's instructions; they
mention several ways to swap the control and caps-lock keys.
Daniel
--
Daniel Barclay
dsb@smart.net
next prev parent reply other threads:[~2003-10-01 16:43 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-01 8:03 C-f, C-b, C-n and C-p or right, left, down, up? Barman Brakjoller
2003-10-01 8:43 ` Noufal Ibrahim
2003-10-01 10:16 ` David Kastrup
2003-10-01 17:02 ` Daniel B.
[not found] ` <mailman.949.1065027827.21628.help-gnu-emacs@gnu.org>
2003-10-01 17:39 ` David Kastrup
2003-10-02 16:16 ` Hans-Christoph Wirth
2003-10-07 18:33 ` David Steuber
2003-10-03 10:31 ` Daniel B.
2003-10-08 23:52 ` Jim Janney
2003-10-09 18:50 ` Barry Margolin
2003-10-16 21:07 ` Kai Grossjohann
2003-10-07 18:29 ` David Steuber
2003-10-09 17:11 ` Daniel B.
[not found] ` <mailman.1425.1065719518.21628.help-gnu-emacs@gnu.org>
2003-10-09 19:42 ` David Steuber
2003-11-03 2:34 ` David Combs
2003-10-01 12:00 ` Arjan Bos
2003-10-01 15:48 ` Barry Margolin
2003-10-02 14:21 ` Arjan Bos
2003-10-06 17:30 ` Gareth Rees
2003-10-01 12:34 ` Stefan Monnier
2003-10-01 12:48 ` Jay Belanger
2003-10-07 18:40 ` David Steuber
2003-10-07 20:02 ` Stefan Monnier
2003-10-07 21:11 ` David Kastrup
2003-10-08 8:48 ` Oliver Scholz
2003-10-08 10:21 ` Eli Zaretskii
[not found] ` <mailman.1313.1065608391.21628.help-gnu-emacs@gnu.org>
2003-10-08 10:27 ` David Kastrup
2003-10-08 15:47 ` Barry Margolin
2003-10-09 18:16 ` C-f, C-b, C-n and C-p or right, left, down, up? - OT now Daniel B.
[not found] ` <mailman.1429.1065723394.21628.help-gnu-emacs@gnu.org>
2003-10-09 19:03 ` Björn Lindström
2003-10-09 20:39 ` C-f, C-b, C-n and C-p or right, left, down, up? lawrence mitchell
2003-10-09 18:15 ` Daniel B.
2003-10-01 12:36 ` Jim Ottaway
2003-10-01 15:07 ` Kevin Rodgers
2003-10-01 16:43 ` Daniel B. [this message]
2003-10-02 13:59 ` Arthur Davis
[not found] ` <mailman.985.1065065051.21628.help-gnu-emacs@gnu.org>
2003-10-02 8:40 ` Matthias Meulien
2003-10-03 10:31 ` Daniel B.
[not found] ` <mailman.1056.1065177296.21628.help-gnu-emacs@gnu.org>
2003-10-16 21:03 ` Kai Grossjohann
2003-10-16 21:13 ` lawrence mitchell
2003-10-06 14:21 ` Sven Utcke
2003-10-06 15:35 ` Barry Margolin
2003-10-07 16:29 ` Hans-Christoph Wirth
2003-10-07 21:11 ` David Kastrup
2003-10-09 15:17 ` Per Abrahamsen
2003-10-09 17:08 ` Daniel B.
[not found] <E1A4kP0-00064x-AV@monty-python.gnu.org>
2003-10-02 22:45 ` Joe Corneli
[not found] ` <mailman.1038.1065134760.21628.help-gnu-emacs@gnu.org>
2003-10-06 14:23 ` Sven Utcke
-- strict thread matches above, loose matches on Subject: below --
2003-10-16 22:32 Joe Corneli
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=3F7B041D.C0048AB@smart.net \
--to=dsb@smart.net \
--cc=help-gnu-emacs@gnu.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.
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).