Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!usc!cs.utexas.edu!uunet!tellab5!grj
From: grj@tellab5.TELLABS.COM (Gary Jenkins)
Newsgroups: comp.sys.amiga
Subject: Re: Problems with STEVIE (The text editor, not the Amiga ad kid)
Message-ID: <1755@tellab5.TELLABS.COM>
Date: 12 Nov 89 16:47:57 GMT
References: <5690@cbnewsh.ATT.COM>
Reply-To: grj@tellab5.UUCP (Gary Jenkins)
Distribution: usa
Organization: Tellabs, Inc. Lisle IL
Lines: 28

In article <5690@cbnewsh.ATT.COM> doug@cbnewsh.ATT.COM (douglas.sulpy) writes:
>I was working on a text file earlier, when Stevie suddenly bombed
>out with the message: "alloc () - not enough chip memory - should 
>never happen".
>Cute. The file in question was around 480 lines - not enough to
>eat up the 1 Meg in my stock 2000. I wasn't running anything
>else, although I HAD had the Bridgecard up earlier (which I
>closed down). Any ideas?

I haven't seen this particular Stevie bug, but I continually get bitten
by another one that everyone should be aware of.  While editing a file, try
writing out a range of lines through colon mode, i.e.

:46,52w somename

Be VERY careful when you leave Stevie.  If you simply do a ZZ, Stevie
will incorrectly assume that your previous write was to the original file
and thus had already saved any changes you had made, so when you do
a ZZ, Stevie will just quit, not write then quit.   Stevie should check
for the filename when you write a file allowing it to know when changes
have really been saved.  I can't count the number to times I have made
drastic changes to a file, wrote out a subsection so it could be included
by another file, then simply ZZ'd out of Stevie.  I was not amused by the
discarding of my changes.

I'm using version 3.35A.  I know there is a newer version out, but it didn't
seem to have this bug fixed, and introduced a new bug with the setlist
and setnumber commands, so I never used it.