Path: utzoo!utgpu!watmath!att!tut.cis.ohio-state.edu!purdue!mentor.cc.purdue.edu!j.cc.purdue.edu!nwd
From: nwd@j.cc.purdue.edu (Daniel Lawrence)
Newsgroups: comp.emacs
Subject: Re: MicroEMACS 3.10 bugs, fixes and a MAJOR improvement to file completion
Summary: uEMACS function keys and ANSI
Keywords: uEMACS 3.10
Message-ID: <9852@j.cc.purdue.edu>
Date: 15 Aug 89 13:41:26 GMT
References: <234@insyte.UUCP> <9847@j.cc.purdue.edu> <1675@crdgw1.crd.ge.com>
Reply-To: nwd@j.cc.purdue.edu (Daniel Lawrence)
Organization: Purdue University
Lines: 20

In article <1675@crdgw1.crd.ge.com> davidsen@crdos1.UUCP (bill davidsen) writes:
>  I would humbly suggest that the previous ANSI sequence capability be
>restored in addition to the TERMCAP stuff. Let the user compile for one
>or the other. Some of us have very complex keyboards and want to use all
>the functions.
>	bill davidsen		(davidsen@crdos1.crd.GE.COM)
>  {uunet | philabs}!crdgw1!crdos1!davidsen
>"Stupidity, like virtue, is its own reward" -me

	How about a comprimise here....  let the TCAP module scan for the
termcap entries, and if a particular escape sequence is not in the termcap,
use some standard translation rule... perhaps mapping it into the ALT area?
Then the termcap keys will always be bound to the standard, machine
independant bindings, and all the unusual  sequences generated on some
TTYs can still be used.

			Daniel Lawrence  voice: (317) 742-5153
					  arpa:	dan@midas.mgmt.purdue.edu
				The Programmer's Room 
				Fido: 1:201/10 - (317) 742-5533