[Coco] Minted buffer size

[Luis Antoniosi (CoCoDemus)]

on minted when a memory allocation fails it tries first to delete your
oldest undo item. When all undos are gone, then it will show the memory
full message.

The memory could be just fragmented. The thing to do when memory is full is
to save the file. Reloading it again could give you some memory extra but
it will report the error soon again.

Luis Felipe Antoniosi



On Sat, Mar 7, 2015 at 11:56 PM, Bill Pierce via Coco <coco at maltedmedia.com>
wrote:

>
> Stephen, I have never said I used an editor with no line limit, though I
> was looking for one at one time. I have always (since about 89 or 90?) used
> "Ed 3.0" by Mike Sweet (author of CGFX7 C library) which has about the same
> buffer size as TSEdit (or vim/vi). The reason I like Ed is it's a menu
> driven full screen editor and not line oriented. Ed also supports tabs,
> cut/copy/paste, and mouse. It's also stable (as most of Mike's stuff was).
> Not a bunch of commands to remember, though control keys are available for
> most functions. And No... it is not an OSk editor. It was written on a
> Coco, for the Coco in OS9 L2 C code.
>
> For a "no line limit" editor in OS9, you would have to go with "DynaStar"
> (Frank Hogg?) or "ScreenStar" (Spectra Systems?), both of which load their
> buffer dynamically from disk and have no file size limit. Both are similar
> to "WordStar" and have high learning curves.
>
>
> Bill Pierce
> "Today is a good day... I woke up" - Ritchie Havens
>
>
> My Music from the Tandy/Radio Shack Color Computer 2 & 3
> https://sites.google.com/site/dabarnstudio/
> Co-Contributor, Co-Editor for CocoPedia
> http://www.cocopedia.com/wiki/index.php/Main_Page
> E-Mail: ooogalapasooo at aol.com
>
>
>
>
> -----Original Message-----
> From: Stephen H. Fischer <SFischer1 at Mindspring.com>
> To: CoCoList for Color Computer Enthusiasts <coco at maltedmedia.com>
> Sent: Sat, Mar 7, 2015 11:23 pm
> Subject: Re: [Coco] Minted buffer size
>
> I used it at lot when I
> was using a real CoCo and though I had made it bullet proof, but as many
> times
> you said you fired a gun one Saturday, perhaps not.
>
> More details would be
> interesting but then perhaps not as it has been so many years since I
> looked at
> the code.
>
> The version I started with was from one of the OS-9 user disks and
> was a real horror and I lost editing sessions many times until it was
> somewhat
> stable.
>
> We users tend to use programs in ways the author never did so I might
> have missed something.
>
> I gave it to a local CoCo Software collector (Thief) who
> gave it to a few friends but I never got any feedback or help with the
> documentation that was promised.
>
> All I can say is what a Doctor said when the
> patent said it hurt when he raised his arm over his head. "Don't do
> that."
>
> Series File Output (ALT CTRL O)  is what I would use to save the current
> editing session to a file ever so often, there is no room for a timed
> version
> like my word processor does.
> -------------------------------------
> Bill Pierce
> once said he was using  an editor with no line limit but thinking about
> that I
> do wonder if he was actually using a OSK version.
>
> Your comment about "editors
> that can handle 100 megabyte files." Is how I handle the problem.
>
> I have the
> "C" source code from Dr. Dobbs for "RED" which could handle files bigger
> than
> memory.
>
> We lost a lot of talent when OSK came out and the people who could have
> fixed many of the things troubling us just left just like I did when
> Borland
> Turbo 'C" showed that there was a better way.
>
> SHF
>
>
>
> --
> Coco mailing
> list
> Coco at maltedmedia.com
> https://pairlist5.pair.net/mailman/listinfo/coco
>
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> https://pairlist5.pair.net/mailman/listinfo/coco
>