unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: "Herbert Euler" <herberteuler@hotmail.com>
Subject: RE: C-p, C-b, C-f, and C-n... why?
Date: Wed, 30 Nov 2005 13:55:40 +0800	[thread overview]
Message-ID: <BAY112-F95ABE85E851C31436C765DA4A0@phx.gbl> (raw)
In-Reply-To: <1133329096.909577.80790@g43g2000cwa.googlegroups.com>

First of all, some terms (especially the ones with which you log
into a remote server) do not support arrow keys. Some keyboard
do not have arrow keys.

Secondly, you might not need to get used to other keystrokes
after you will be familiar with Emacs, since you could find Emacs
is able to finish a lot of kinds of jobs conveniently so that you
don't need other editors.

Regards,
Guanpeng Xu

_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today it's FREE! 
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/

  reply	other threads:[~2005-11-30  5:55 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 [this message]
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
     [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=BAY112-F95ABE85E851C31436C765DA4A0@phx.gbl \
    --to=herberteuler@hotmail.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).