Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!iuvax!purdue!mentor.cc.purdue.edu!j.cc.purdue.edu!nwd
From: nwd@j.cc.purdue.edu (Daniel Lawrence)
Newsgroups: comp.emacs
Subject: Re: Next MicroEmacs version (problems)
Summary: uEMACS on System V
Keywords: uEMACS UNIX V5
Message-ID: <10011@j.cc.purdue.edu>
Date: 7 Sep 89 21:16:49 GMT
References: <1329@syma.sussex.ac.uk> <9993@j.cc.purdue.edu> <14078@bloom-beacon.MIT.EDU> <786@coplex.UUCP>
Reply-To: nwd@j.cc.purdue.edu (Daniel Lawrence)
Organization: Purdue University
Lines: 39

In article <786@coplex.UUCP> dean@coplex.UUCP (Dean Brooks) writes:
>  I am a die-hard MicroEmacs user.  Have been for almost 3 years.  It is
>definitely the best small-scaled editor ever produced.

>  However, I do have one MAJOR complaint that I hope any future versions of
>MicroEmacs will fix.  MicroEmacs version 3.10 has TERRIBLE Meta-Key
>translating routines that used to be WONDERFUL in version 3.9  We are
>running MicroEmacs on UNIX 5.2 and have been for almost 3 years.

>  I ended up having to delete the Meta-Key routines from 3.10 and merge
>in the ones from 3.9 because it wouldn't correctly accept a Meta-Key
>that was equal to an ESCAPE character.  Thus it would get confused
>between functions-keys and bound commands.  No function keys or special
>keys would work (such as NEXT-PAGE keys, etc.)

>  Dont get me wrong, I LOVE MicroEmacs.  I just hope that this problem
>gets resolved in future versions.  It makes it very difficult to run
>on character-based terminals (i.e. Wyse-60's, etc.).

	The routines in version 3.9 produced machine specific code that
made macroes non-portable between MicroEMACS implimentations.  Version's
3.10 effort to standardize these is very neccessary.  The actually
problem you are experiencing is my lack of a UNIX system V nap()
function which is portable, and the fact that I do not have access to a
system V implimentation and all its documentation so that I can attempt
to find another way to do the same thing.

	So once again, if the system V and XENIX fans out there are
unhappy with support for thier machines under XENIX or system V, someone
needs to help me get a system V OS for my development machine. 
Maintaining and distributing MicroEMACS is a finacial disaster on my
part, and has been for four years now.  If the XENIX people out there
band together to get me a XENIX, they would find much better support for
XENIX and system V.

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