Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ames!hc!lll-winken!uunet!ispi!jbayer
From: jbayer@ispi.UUCP (Jonathan Bayer)
Newsgroups: comp.emacs
Subject: Re: Grrr... uEmacs 3.10 doesn't work under Xenix
Keywords: uEMACS 3.10
Message-ID: <588@ispi.UUCP>
Date: 12 Apr 89 12:08:37 GMT
References: <56344@yale-celray.yale.UUCP> <9313@j.cc.purdue.edu> <13576@steinmetz.ge.com>
Reply-To: jbayer@ispi.UUCP (Jonathan Bayer)
Organization: Intelligent Software Products, Inc.
Lines: 27

In article <13576@steinmetz.ge.com> davidsen@crdos1.UUCP (bill davidsen) writes:
>
>  I think we may have failed to make it clear that support for ANSI
>keysequences is needed in UNIX versions. Termcap support won't do it. I
>posted fixes for this in every version from 3.7? to 3.10beta and none of
>them ever got picked up.

Why?  What is the matter with reading the termcap entry and interpreting
the keys according to the termcap info?  Why must the keys for ANSI be
hardcoded into the program, therefore increasing the program size and
complexity?  I have been able to make version 3.10 work with all the
keys on my keyboard by simply installing the appropriate modification to
my termcap file. (For those who don't know the modification added the
function key definitions to the termcap entry).  By using the termcap
entry it is now possible to use eEmacs on several different terminals,
and being able to use whatever function keys are available knowing that
their function will be the same.  I think that the current solution is
much better than a hardcoded one.



JB
-- 
Jonathan Bayer			      Beware: The light at the end of the
Intelligent Software Products, Inc.	      tunnel may be an oncoming dragon
19 Virginia Ave.				...uunet!ispi!jbayer
Rockville Centre, NY 11570  (516) 766-2867    jbayer@ispi.UUCP