unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Peter Dyballa <Peter_Dyballa@Web.DE>
To: Tyler Smith <tyler.smith@mail.mcgill.ca>
Cc: help-gnu-emacs@gnu.org
Subject: Re: arrow keys in the console
Date: Sat, 19 May 2007 16:37:33 +0200	[thread overview]
Message-ID: <0B112858-D4C7-41DB-91EF-7A349BAD146A@Web.DE> (raw)
In-Reply-To: <slrnf4stig.ct6.tyler.smith@blackbart.mynetwork>


Am 19.05.2007 um 05:00 schrieb Tyler Smith:

>>> tset - -Q or such can determine the right value. It also would work
>>> to set it xterm or xterm-color. This kind of terminal is supported
>>> by GNU Emacs. Look into lisp/term directory!
>>>
>>> --
>> NO! This will not work correctly for a GNU Linux console. The TERM
>> setting of 'Linux', is *correct* for the console - do not change
>> it. The problem is with keymaps. Load the correct keymap and the
>> problem is solved.
>>
>
> Well, you're right. Setting TERM=xterm fixed the arrow keys, but
> page-up and page-down still act funny.

Open ~/.emacs and then work on this loop:

	M-x global-set-key RET <press the key> RET <function binding> RET
	C-x Esc Esc C-a C-k C-g		; repeat last command, beginning, kill  
line, quit
	C-x b .emacs RET
	C-y

Finally save ~/.emacs.

The cursor movement functions are previous-line, next-line, backward- 
char, and forward-char.


Since there is a file /usr/local/share/emacs/22.1.50/lisp/term/ 
linux.el I wonder whether it's worth to write a bug report about the  
behaviour of your GNU Emacs in that "linux" terminal. It would be  
worth to mention the actual key bindings of your system!

--
Greetings

   Pete

When confronted with actual numbers, a mathematician is at a loss.
                                          (Steffen Hokland)

  reply	other threads:[~2007-05-19 14:37 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-18  1:00 arrow keys in the console Tyler Smith
2007-05-18  7:25 ` Pascal Bourguignon
2007-05-18 12:16   ` Tyler Smith
2007-05-18 12:37     ` poppyer
2007-05-18 14:00     ` Peter Dyballa
2007-05-18 15:14       ` Tyler Smith
     [not found]       ` <mailman.807.1179498154.32220.help-gnu-emacs@gnu.org>
2007-05-19  3:03         ` Tim X
2007-05-19  3:14           ` Tyler Smith
2007-05-19  4:54             ` Tim X
2007-05-19  2:38     ` Tim X
     [not found]     ` <mailman.805.1179497353.32220.help-gnu-emacs@gnu.org>
2007-05-19  2:41       ` Tim X
2007-05-19  3:00         ` Tyler Smith
2007-05-19 14:37           ` Peter Dyballa [this message]
     [not found]           ` <mailman.860.1179585463.32220.help-gnu-emacs@gnu.org>
2007-05-19 14:58             ` poppyer
2007-05-19 14:59             ` Tyler Smith
2007-05-19 17:22               ` Peter Dyballa
     [not found]               ` <mailman.872.1179595364.32220.help-gnu-emacs@gnu.org>
2007-05-20 15:43                 ` Tyler Smith
2007-05-21 12:03                 ` Will Parsons
2007-05-22  4:38           ` Xavier Maillard

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=0B112858-D4C7-41DB-91EF-7A349BAD146A@Web.DE \
    --to=peter_dyballa@web.de \
    --cc=help-gnu-emacs@gnu.org \
    --cc=tyler.smith@mail.mcgill.ca \
    /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).