The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: bqt@softjar.se (Johnny Billquist)
Subject: [pups] jove editor under 2.11BSD and cursor keys
Date: Mon, 05 Jan 2009 00:59:42 +0100	[thread overview]
Message-ID: <49614D6E.2090408@softjar.se> (raw)
In-Reply-To: <496116C4.8050101@gsi.de>

Walter F. Mueller wrote:
> Hello,
> 
> I'm using the jove editor under 2.11BSD, the jove release is
> from 1988. It works just fine, except for the cursor keys.
> Even though the ansi-codes function is properly bound,
> 'ESC x describe-bindings' shows:
> 
>      ESC [  ansi-codes
> 
> I get whenever I hit one of the cursor keys the message
> 
>      [ESC O unbound]
> 
> TERM is set to vt100, termcap is ok, and the xterm used is
> started with -ti vt100. vi for example works and accepts the
> cursor keys, a dump of the chars emitted by xterm show that
> the proper \[[A ect sequence indeed arrives.
> 
> Any help or hint on how to get this to work is very much
> appreciated.

Please note the difference between "<ESC>[" and "<ESC>O"... :-)

To give you a little more help: someone or something is changing your 
terminal to have application cursor keys.
(And to point out what should be obvious now: your cursor keys can 
actually send two different kind of codes, depending on a setup parameter.)

	Johnny



  reply	other threads:[~2009-01-04 23:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-04 17:49 [pups] 2.11BSD Patch 446+447; fixes for ulrem,umount,tar,tcsh,ps,vmstat,apropos,pstat,rk Walter F. Mueller
2009-01-04 20:06 ` [pups] jove editor under 2.11BSD and cursor keys Walter F. Mueller
2009-01-04 23:59   ` Johnny Billquist [this message]
2009-01-05 20:06     ` Walter F.J. Mueller
2009-01-06 16:49       ` robinb
2009-01-06 16:54         ` Johnny Billquist

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=49614D6E.2090408@softjar.se \
    --to=bqt@softjar.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 NNTP newsgroup(s).