From: Lute Kamstra <Lute.Kamstra@cwi.nl>
Subject: Re: Control key vs arrow keys
Date: 05 Sep 2002 23:06:02 +0200 [thread overview]
Message-ID: <sgd4rd4tadh.fsf@occarina.pna.cwi.nl> (raw)
In-Reply-To: <VbPd9.9722$6i4.788990@newsread1.prod.itd.earthlink.net>
"gamaz" <gamaz@earthlink.net> writes:
> I was wondering what is the reason for the preferred use of the
> control key as against keyboard's arrow key?
Do you mean the use of C-f to go one character forward? I think it's
a relic of the time when keyboards did not have arrow keys. Now, most
keyboards do and you can also go a character forward with the right
arrow key. Quite a number of people still use the C-f variant since
the control and the f key are usually closer at hand.
Lute.
--
(spook) => "LLNL ASPIC White House"
(insert-file-contents "~/.signature") => (error "`~/.signature' too rude")
next prev parent reply other threads:[~2002-09-05 21:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-05 20:32 Control key vs arrow keys gamaz
2002-09-05 21:06 ` Lute Kamstra [this message]
2002-09-06 2:22 ` Miles Bader
-- strict thread matches above, loose matches on Subject: below --
2002-09-06 6:17 Dmitri.Minaev
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=sgd4rd4tadh.fsf@occarina.pna.cwi.nl \
--to=lute.kamstra@cwi.nl \
/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).