Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!think!nike!ucbcad!ucbvax!CORY.BERKELEY.EDU!dillon
From: dillon@CORY.BERKELEY.EDU (Matt Dillon)
Newsgroups: net.micro.mac
Subject: Re: VI features, Editors, etc...
Message-ID: <8610161628.AA29198@cory.Berkeley.EDU>
Date: Thu, 16-Oct-86 12:28:16 EDT
Article-I.D.: cory.8610161628.AA29198
Posted: Thu Oct 16 12:28:16 1986
Date-Received: Thu, 16-Oct-86 22:56:23 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: University of California at Berkeley
Lines: 23

>From: guido@mcvax.uucp (Guido van Rossum)
>Oh yeah?  Wait till mouse-based editors have been around as long and
>hacked as much as VI...  Are we just discussing the merits of existing
>editors or also the potential of different paradigms?  Why would it be
>impossible to add complete mouse support and standard cut/paste to an
>Emacs-like editor?

	We are discussing the potential of different user interfaces for
editors.  Specifically, I was talking about word processing / programming,
not drawing or paint programs .

	You said it, I didn't. "add complete".  The point is that it would
then not be solely based on the mouse, but rely on the keyboard for the more
complex commandsd .  I believe I covered this in my last posting.  The fact
is that an editor which allows the user to choose between the keyboard and
mouse, or use BOTH the keyboard and the mouse, has the potential to beat out
everything else in existance (or at least within the scope of our 
discussion).  Such an editor should allow you to use the mouse and keyboard
interchangably (not be dependant on either) for command entry (obviously you
need the keyboard for text entry).  The editor which uses the mouse 
exclusively for command entry comes dead last in my list.

						-Matt