Path: utzoo!attcan!uunet!samsung!sol.ctr.columbia.edu!src.honeywell.com!gumby!pclark
From: pclark@SRC.Honeywell.COM (Peter Clark)
Newsgroups: comp.sys.next
Subject: Re: MailManager
Message-ID: <1990Nov5.204606.11740@src.honeywell.com>
Date: 5 Nov 90 20:46:06 GMT
References: <670@mara.cognet.ucla.edu> <10577@milton.u.washington.edu> <1873@kgw2.bwi.WEC.COM>
Sender: news@src.honeywell.com (News interface)
Organization: Honeywell Systems & Research Center
Lines: 17
In-Reply-To: dennisg@kgw2.bwi.WEC.COM's message of 5 Nov 90 14:13:15 GMT
Nntp-Posting-Host: gumby.src.honeywell.com

>|> In article <670@mara.cognet.ucla.edu> iwelch@agsm.ucla.edu (Ivo Welch) writes:
>|> 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
>|> ...
>|> 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.
>

I believe that some emacs keybindings (basic ones, like ctrl-f, ctrl-b,
etc...) are part of the 2.0 Text object.

	Pete Clark