From: Peter Dyballa <Peter_Dyballa@Web.DE>
Cc: help-gnu-emacs@gnu.org
Subject: Re: C-p, C-b, C-f, and C-n... why?
Date: Sat, 10 Dec 2005 23:40:23 +0100 [thread overview]
Message-ID: <0bcf8e6b891934f30c52bb9af6221728@Web.DE> (raw)
In-Reply-To: <11pmkm7sol448a9@corp.supernews.com>
Am 10.12.2005 um 23:13 schrieb roodwriter@core.com:
> I think the tutorial should start with the arrow keys and then give
> the commands as options and the history behind them.
>
In (computer) history the arrow (cursor) keys came later ... and the
tutorial is historically grown!
I too prefer mostly the arrow keys (and mouse cursor). Their use is too
obvious to mention them that early in the tutorial, mentioning them
could be done in a footnote. The recent state is fine in one particular
sense: M-up does not scroll back in *shell* buffer's command history
(because it's undefined); only M-p does. So I think it's necessary to
teach C-{b,f,n,p} first to remember this as a way "move" in many
things, in many sense.
--
Greetings
Pete
"What is this talk of 'release'? Klingons do not make software
'releases'. Our software 'escapes' leaving a bloody trail of
designers and quality assurance people in its wake."
next prev parent reply other threads:[~2005-12-10 22:40 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
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 [this message]
[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=0bcf8e6b891934f30c52bb9af6221728@Web.DE \
--to=peter_dyballa@web.de \
--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).