unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Fredrik Staxeng <fstx+u@update.uu.se>
Subject: Re: S-up and emacs -nw?
Date: 20 Oct 2002 19:10:10 +0200	[thread overview]
Message-ID: <1m1y6l3ukt.fsf@Tempo.Update.UU.SE> (raw)
In-Reply-To: u4rbhf6ab.fsf@terrapin.northbound-train.com

"Joe Casadonte" <jcasadonte@northbound-train.com> writes:

>Fredrik,
>
>On 20 Oct 2002, Fredrik Staxeng wrote:
>
>> Then your are halfway there. Now you just need to assign a function
>> to f14. Use define-key or global-set-key as appropriate. They
>> keys that Emacs does not see at all, or see as another key, need
>> to be changed using loadkeys.
>
>I'm almost there.  If:
>
>1) the kernel knows that UP is "<ESC>[A"
>2) I teach the kernel (via loadkeys) that Shift-Up is "<ESC>[a"
>3) Emacs knows that <up> is bound to `previous-line-nomark' and
>   <S-up> is bound to `previous-line-mark'
>
>How do I get Emacs to recognize "<ESC>[a" as <S-up>, so that I don't
>have to do some crazy conditional keybindings?  Should I use
>`keyboard-translate' for that?  If so, how would I represent "<ESC>[a"
>as a character?

Crazy conditional keybindings is probably an equivalent amount of work,
unless you need to do mode-specific bindings. But the see the files
in the subdirectory term of your lisp directory. It seems
that you can do things like 

(define-key function-key-map "\e[161q" [S-up])

If you run debian, you need to install the emacs21-el package to get 
the lisp source files.

There seems to be a sizeable number of people still running in tty 
mode. I guess about 1% of those run on actual terminals, the rest
are runnning various terminal emulators. 

-- 
Fredrik Stax\"ang | rot13: sfgk@hcqngr.hh.fr

  reply	other threads:[~2002-10-20 17:10 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-13 20:39 S-up and emacs -nw? Joe Casadonte
2002-10-13 21:09 ` Stefan Monnier <foo@acm.com>
2002-10-14  2:18   ` Joe Casadonte
2002-10-14  4:09     ` Stefan Monnier <foo@acm.com>
2002-10-14  5:49       ` Fredrik Staxeng
2002-10-14 13:45       ` Joe Casadonte
2002-10-14 15:08         ` Ehud Karni
2002-10-14 15:34         ` Stefan Monnier <foo@acm.com>
2002-10-14 18:56         ` Fredrik Staxeng
2002-10-14 20:00         ` Alan Mackenzie
     [not found]         ` <mailman.1034608215.19174.help-gnu-emacs@gnu.org>
2002-10-19 13:05           ` Joe Casadonte
2002-10-19 16:44             ` Fredrik Staxeng
2002-10-19 21:03               ` Joe Casadonte
2002-10-20 12:33                 ` Fredrik Staxeng
2002-10-20 15:08                   ` ken
2002-10-20 16:01                   ` Joe Casadonte
2002-10-20 17:10                     ` Fredrik Staxeng [this message]
2002-10-21  0:24                       ` Joe Casadonte
2002-10-21 22:01                       ` Alan Mackenzie
2002-10-22  7:12                         ` Fredrik Staxeng
2002-10-22 18:58                           ` Alan Mackenzie
2002-10-21 13:22             ` Stefan Monnier <foo@acm.com>
2002-10-14 18:47     ` Alex Schroeder

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=1m1y6l3ukt.fsf@Tempo.Update.UU.SE \
    --to=fstx+u@update.uu.se \
    /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).