From: Harald Hanche-Olsen <hanche@math.ntnu.no>
Subject: Re: C-p, C-b, C-f, and C-n... why?
Date: Wed, 30 Nov 2005 10:32:14 +0100 [thread overview]
Message-ID: <pcod5kiqy5d.fsf@shuttle.math.ntnu.no> (raw)
In-Reply-To: 1133329096.909577.80790@g43g2000cwa.googlegroups.com
+ casioculture@gmail.com:
| In the tutorial it suggests I use C-p, C-b, C-f, and C-n rather than
| arrow keys, why should i?
If you don't want to, don't. The tutorial is very old. As others
have explained, some keyboards don't have arrow keys, and with some
network connections, they may not work even if you have them. But
this is much less a problem now than it was twenty years ago.
Personally, I use both arrow keys and C-p etc. The latter have the
advantage that I don't need to move my hands to type them. The arrow
keys have the advantage that they are bunched close together, so I
prefer them when I have lots of movement to do. (But then other
movement commands may be more useful, such as M-f, M-b, M-a, M-e.)
| Trying to get used to this is such a pain. It's ludicrous.
Don't force yourself into doing something you're uncomfortable with.
Now /that/ is ludicrous.
--
* Harald Hanche-Olsen <URL:http://www.math.ntnu.no/~hanche/>
- Debating gives most of us much more psychological satisfaction
than thinking does: but it deprives us of whatever chance there is
of getting closer to the truth. -- C.P. Snow
next prev parent reply other threads:[~2005-11-30 9:32 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-30 5:38 C-p, C-b, C-f, and C-n... why? casioculture
2005-11-30 5:55 ` Herbert Euler
2005-11-30 8:16 ` Lennart Borgman
2005-11-30 8:39 ` Alan Mackenzie
2005-11-30 9:32 ` Harald Hanche-Olsen [this message]
2005-11-30 11:58 ` Thien-Thi Nguyen
2005-11-30 13:21 ` David Hansen
2005-11-30 21:07 ` Eli Zaretskii
2005-11-30 21:49 ` Tim Johnson
2005-12-09 22:03 ` Edward Dodge
2005-12-10 9:51 ` Xavier Maillard
2005-12-10 22:13 ` roodwriter
2005-12-10 22:40 ` Peter Dyballa
[not found] ` <mailman.18736.1134254458.20277.help-gnu-emacs@gnu.org>
2005-12-10 23:09 ` roodwriter
2005-12-10 23:12 ` Lennart Borgman
2005-12-11 4:18 ` Eli Zaretskii
[not found] ` <mailman.18760.1134274741.20277.help-gnu-emacs@gnu.org>
2005-12-12 11:59 ` Mathias Dahl
2005-12-12 21:04 ` Eli Zaretskii
2005-12-12 22:32 ` Lennart Borgman
2005-12-12 23:22 ` Tim Johnson
[not found] ` <mailman.19039.1134421524.20277.help-gnu-emacs@gnu.org>
2005-12-13 8:28 ` Mathias Dahl
2005-12-13 8:56 ` Ralf Angeli
2005-12-13 17:27 ` Tim Johnson
2005-12-13 20:27 ` Eli Zaretskii
2005-12-15 20:36 ` Björn Lindström
2005-12-15 23:26 ` Xavier Maillard
2005-12-17 10:52 ` don provan
[not found] ` <mailman.19488.1134911034.20277.help-gnu-emacs@gnu.org>
2005-12-19 9:24 ` Mathias Dahl
2005-12-15 6:15 ` Stefan Monnier
2005-12-15 9:21 ` Mathias Dahl
2005-12-15 12:01 ` Per Abrahamsen
2005-12-15 16:47 ` Drew Adams
2005-12-15 18:28 ` Mathias Dahl
2005-12-15 20:43 ` Lennart Borgman
2005-12-15 13:15 ` Lennart Borgman
2005-12-15 17:40 ` Xavier Maillard
2005-12-15 17:52 ` Lennart Borgman
2005-12-16 17:46 ` Richard M. Stallman
2005-12-15 19:18 ` Eli Zaretskii
-- strict thread matches above, loose matches on Subject: below --
2005-11-30 5:52 Dave Humphries
[not found] <mailman.17286.1133329946.20277.help-gnu-emacs@gnu.org>
2005-11-30 11:08 ` David Kastrup
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=pcod5kiqy5d.fsf@shuttle.math.ntnu.no \
--to=hanche@math.ntnu.no \
/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).