Path: utzoo!attcan!uunet!kgw2!dennisg
From: dennisg@kgw2.bwi.WEC.COM (Dennis Glatting)
Newsgroups: comp.sys.next
Subject: Re: MailManager
Message-ID: <1873@kgw2.bwi.WEC.COM>
Date: 5 Nov 90 14:13:15 GMT
References: <670@mara.cognet.ucla.edu> <10577@milton.u.washington.edu>
Sender: dennisg@kgw2.bwi.WEC.COM
Reply-To: dennisg@kgw2.bwi.WEC.COM
Organization: Xetron Corporation, Cincinnati Ohio
Lines: 24


In article <10577@milton.u.washington.edu>, mrc@Tomobiki-Cho.CAC.Washington.EDU (Mark Crispin) writes:
|> In article <670@mara.cognet.ucla.edu> iwelch@agsm.ucla.edu (Ivo Welch) writes:
|> >I have recently pulled MailManager  from purdue. It  is a great  program
|> 
|> 
|> I have been asking NeXT for a long long time to support VI and EMACS
|> within Text objects.  I consider this to be an Application Kit missing
|> feature.  I consider it to be wrong for every single program to
|> implement its own EMACS emulator (or interface into EMACS) with its
|> own pecularities.  Also, doing an EMACS interface without a VI one is
|> bound to annoy VI fanatics, and vice versa.
|> 
|> Help me by bugging NeXT to put a general editor interface into Text
|> objects!

 why don't you just write one?  subclass Text or create an new object.  call
it TermcapText.



--
 ..!uunet!kgw2!dennisg      | Dennis P. Glatting
 dennisg@kgw2.bwi.WEC.COM   | X2NeXT developer