Path: utzoo!utgpu!watmath!att!tut.cis.ohio-state.edu!rutgers!cs.utexas.edu!uunet!crdgw1!sungod!davidsen
From: davidsen@sungod.crd.ge.com (ody)
Newsgroups: comp.emacs
Subject: Re: MicroEMACS 3.10 bugs, fixes and a MAJOR improvement to file completion
Keywords: uEMACS 3.10
Message-ID: <1675@crdgw1.crd.ge.com>
Date: 15 Aug 89 12:55:53 GMT
References: <234@insyte.UUCP> <9847@j.cc.purdue.edu>
Sender: news@crdgw1.crd.ge.com
Reply-To: davidsen@crdos1.UUCP (bill davidsen)
Organization: General Electric Corp. R&D, Schenectady, NY
Lines: 26

In article <9847@j.cc.purdue.edu> nwd@j.cc.purdue.edu (Daniel Lawrence) writes:

| >5) For tcap.c, it was a good idea to have function key parsing that
| >standardized the names.  However, it is now quite difficult to deal with
| >application keypads.  I use a VT100 like terminal with 8 function keys
| >and an 18 key keypad.  Most of the keypad is wasted since a standard termcap
| >only allows for 10 function keys and a few special keys like delete character,
| >page up/down, etc.  I can't think of a solution so maybe I shouldn't complain.
| 
| 	Someone.... send me a VT100! 

  My solution was to stick with 3.9p. When 3.10 first came out it was
obvious that the TERMCAP can't handle large numbers of function keys.
Given F1-F12, shift and control (and ALT in DOS), or a Sun with F1-F9,
L1-L10, and R1-R15 (all of which can be modified with shift, control,
alt, left-meta and right-meta). This is a lot of stuff to put in a
TERMCAP, and works a lot better when you can recognize ANY three
character ANSI sequence (that is, ESCAPE, [, {anything}).

  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