Xref: utzoo comp.sys.amiga:26845 comp.sys.amiga.tech:2855
Path: utzoo!utgpu!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!cwjcc!mailrus!bbn!ulowell!cbmvax!higgin
From: higgin@cbmvax.UUCP (Paul Higginbottom MKT)
Newsgroups: comp.sys.amiga,comp.sys.amiga.tech
Subject: Re: Stevie editor
Message-ID: <5534@cbmvax.UUCP>
Date: 20 Dec 88 15:33:16 GMT
References: <5040.AA5040@heimat> <10499@umn-cs.CS.UMN.EDU>
Reply-To: higgin@cbmvax.UUCP (Paul Higginbottom MKT)
Organization: Commodore Technology, West Chester, PA
Lines: 59

In article <10499@umn-cs.CS.UMN.EDU> brant@uf.msc.umn.edu (Gary Brant) writes:
$In article <5040.AA5040@heimat> sneakers@heimat.UUCP (Dan "Sneakers" Schein) writes:
$>  Ive been using with the editor 'Stevie' posted to the net a few days back
$> and my first impressions are great.

Mine are not.

$> It supports the 'VI' features that I use
$> most, and it seems to be very solid. (Compared to a commercial 'VI' like
$> editor ;-)

It does not seem as solid as a commercial vi or 'z' for that matter.  For
example, I deleted to the end ('D') a line that wrapped, but it did not pull
up the lines below.

But this I could forgive if it wasn't so ABYSMALLY SLOW.  I'm fairly fast at
the keyboard, but this thing can only seem to insert 3 or 4 characters per
second!  And no, I am not running any other "active" tasks (there are other
programs loaded, but they're not doing anything).  

$>  There is one thing however that I find to be a minor problem. It will not
$> allow you to "run" it (IE: 1> run stevie). The error message returned is
$>  [stuff deleted]

I find this reasonable, since running a program doesn't give it any stdio.
It COULD be smart enough to handle this and open its own window, but that
would be an Amiga specific mod.

$I've noticed one additional problem; when I start up Stevie, it hangs until
$I resize the window it is running in.  This is probably due to my morerow'ed
$interlace WorkBench screen.

Probably.  I do not experience this problem.

$Additionally, I have a file of ~1MB size I
$would like to edit but can't even though I start with nearly 2MB ram free;
$it consumes all the free memory (fast and chip) & then gives up.

This I can definitely believe.  If memory is allocated in lines, the
overhead will consume lots of additional RAM, e.g if overhead is 20% per line
(16 bytes for each 80 character line) then 1.2Mb would be required for the 1Mb
file, but in fact, much more will be required because few lines are 80 characters.
A blank line will have 1600% of overhead.

$Otherwise I like this editor very much & hope some one will fix these minor
$annoyances.

Yes, a pd vi that's fast w/ source and as full-featured as this one appears to
be would be great.  Until then, I stick to z, which is fast, fairly full-featured
(: commands need work to handle marks!!!) and small.

$> Sneakers
$-Gary Brant	ARPA: brant@uf.msc.umn.edu
$#include <std/disclaimer.h>

	Paul.

Disclaimer: I have no affiliation with Manx, and this is not an endorsement of
their products by Commodore.  I'm just a vi nut.