From: Dmitri.Minaev@Samara.BritishCouncil.RU
Subject: RE: Control key vs arrow keys
Date: Fri, 6 Sep 2002 10:17:47 +0400 [thread overview]
Message-ID: <B5CFBC051993D41196FF00D0B78EE626DA3BFC@RUS2NT01> (raw)
One reason is telnet(ssh/rsh, etc) + crippled TERM that doesn't understand
some escape sequences.
--
With best regards,
Dmitri Minaev
> -----Original Message-----
> From: gamaz [mailto:gamaz@earthlink.net]
> Sent: Thursday, September 05, 2002 9:33 PM
> To: help-gnu-emacs@gnu.org
> Subject: Control key vs arrow keys
>
>
> I was wondering what is the reason for the preferred use of
> the control key
> as against keyboard's arrow key?
>
> Any help is highly appreciate. Thanks.
>
>
> _______________________________________________
> Help-gnu-emacs mailing list
> Help-gnu-emacs@gnu.org
> http://mail.gnu.org/mailman/listinfo/help-gnu-emacs
>
next reply other threads:[~2002-09-06 6:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-06 6:17 Dmitri.Minaev [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-09-05 20:32 Control key vs arrow keys gamaz
2002-09-05 21:06 ` Lute Kamstra
2002-09-06 2:22 ` Miles Bader
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=B5CFBC051993D41196FF00D0B78EE626DA3BFC@RUS2NT01 \
--to=dmitri.minaev@samara.britishcouncil.ru \
/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).