Path: utzoo!utgpu!water!watmath!clyde!bellcore!faline!thumper!ulysses!andante!mit-eddie!uw-beaver!cornell!rochester!jpayne
From: jpayne@rochester.UUCP
Newsgroups: comp.emacs
Subject: Re: jove & vt100
Message-ID: <9653@sol.ARPA>
Date: 12 May 88 23:14:58 GMT
References: <299@wmt.UUCP> <1040006@acf8.UUCP>
Reply-To: jpayne@cs.rochester.edu (Jonathan Payne)
Organization: U of Rochester, CS Dept, Rochester, NY
Lines: 29
Posted: Thu May 12 19:14:58 1988

In article <1040006@acf8.UUCP> sperling@acf8.UUCP (George Sperling) writes:
>The else is optional. You can use this to check your terminal type in
>the environment. If checkenv is a program that returns 1 whenever
>getenv(argv[2]) matches argv[3], your .joverc should read as follows:
>
>if checkenv TERM vt100
>set meta-key off
>set allow-^S-and-^Q off
>bind-to-key ansi-codes ESC O
>else
>bind-to-key ansi-codes ESC [
>endif


You could go through all this pain, or you could just put both in
the .joverc.  That is,
	bind-to-key ansi-codes ESC [
	bind-to-key ansi-codes ESC O
in the .joverc and not mess with that stupid kludge (called a feature)
that I implemented when I was feeling real dumb.  I tell you, the urge
to write a simple lisp interpreter is so great (!!!) ... but then we'd
end up with two gnu's, and that would be exactly one too many, right?

Jonathan Payne
	
P.S.  But I DIDN'T write the ansi-codes kludge - I just gave in to
pressure and put it in the official version.  I've been meaning to
implement real keymaps, except that I just don't need them because I
don't believe in function keys...