From: pclouds <pclouds@users.sourceforge.net>
Cc: help-gnu-emacs@gnu.org
Subject: Re: tty emacs
Date: Wed, 23 Apr 2003 17:44:31 +0700 [thread overview]
Message-ID: <20030423104431.GA1163@localhost.localdomain> (raw)
In-Reply-To: <f7h58b.s5.ln@acm.acm>
On Wed, Apr 23, 2003 at 08:00:47AM +0000, Alan Mackenzie wrote:
> Niels Freimann <nfreimann@firemail.de> wrote on Wed, 23 Apr 2003 07:38:24
> +0200:
> > Hi,
>
> > emacs in tty mode (emacs -nw) obviously doesn't know
> > C-prior and C-next. I already tried out
> > (define-key function-key-map "\e[40~" [C-prior])
> > (define-key function-key-map "\e[41~" [ C-next])
>
> Presumably you're running in a tty window under X, but under which
> operating system?. I run emacs directly on a Linux tty. I had to remap
> my keyboard (with the program loadkeys) fairly radically to make it
> produce different codes for [right] and [C-right], and so on. Maybe you
> have to do this (or something similar) for emacs -nw.
Could you show me how to do that? I'm using Emacs on a Linux tty too,
and have the same problem with [right], [C-right].
>
> > however its doesn't help. Any idea?
>
> Well, tell us HOW it didn't help. :-) What exactly does happen?
>
> Let me guess: C-prior does exactly the same as prior. After typing
> these two key sequences, do a C-h l ('view-lossage') to see exactly what
> key codes emacs received.
>
> > -Niels
>
> --
> Alan Mackenzie (Munich, Germany)
> Email: aacm@muuc.dee; to decode, wherever there is a repeated letter
> (like "aa"), remove half of them (leaving, say, "a").
>
> _______________________________________________
> Help-gnu-emacs mailing list
> Help-gnu-emacs@gnu.org
> http://mail.gnu.org/mailman/listinfo/help-gnu-emacs
--
Bi Cờ Lao
next prev parent reply other threads:[~2003-04-23 10:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.5101.1051076825.21513.help-gnu-emacs@gnu.org>
2003-04-23 8:00 ` tty emacs Alan Mackenzie
2003-04-23 10:44 ` pclouds [this message]
2003-04-23 5:38 Niels Freimann
2003-04-23 11:18 ` Eli Zaretskii
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030423104431.GA1163@localhost.localdomain \
--to=pclouds@users.sourceforge.net \
--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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.