From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from netcomsv.netcom.com ([192.100.81.101]) by hawkwind.utcs.toronto.edu with SMTP id <2808>; Tue, 24 Nov 1992 00:23:10 -0500
Received: from netapp.UUCP by netcomsv.netcom.com with UUCP (4.1/SMI-4.1)
	id AA23085; Mon, 23 Nov 92 21:18:52 PST
Received: by netapp.netapp.com (4.1/SMI-4.1)
	id AA02410; Mon, 23 Nov 92 21:18:33 PST
Date:	Tue, 24 Nov 1992 00:18:33 -0500
From:	byron@netapp.com (Byron Rakitzis)
Message-Id: <9211240518.AA02410@netapp.netapp.com>
To:	john@civil.su.oz.au, sam-fans@hawkwind.utcs.toronto.edu
Subject: Re: saved replacement texts?

>How about cutting me some slack, Byron?

I got hot because you called Scott's idea "stupid". If you are going to
call something stupid, you should probably know what you're doing
first.  On this side of the Pacific, those are strong words.

>What I think would be appropriate would be for people who've just started
>using the editor since it's been available free to accumulate four years
>worth of experience with it before leaping to suggest how it should be
>improved.

I've used sam here and there for about that long. I have a pretty
good idea of how it works, and I also have a pretty good idea of what
I want.

>It would also be as well to remember that sam's interface was designed
>to integrate nicely with its surrounding window system environment, viz.
>mux on the Jerq.

I am baffled by one point regarding sam: why is it that it must implement
its own mini-window system internally? I agree that it "integrates" well
with mux: by imitating it! Unfortunately this means that sam is a misfit
in just about any other environment.

(For comparision, check out the NeXT editor. It is a multi-file editor
(no command language to speak of though) that opens a separate window
for each file.)