🚀 go-pugleaf

In article <1990Sep24.150432.25049@msuinfo.cl.msu.edu> dailey@frith.uucp (Chris Dailey) writes:
>In article <1990Sep23.174736.16118@lavaca.uh.edu> jet@karazm.math.uh.edu (J. Eric Townsend) writes:
>>It can be done.  It's somewhat bizarre, but it can be done.  Essentially,
>>you keep track of the changes to the file.  You change the file whenever
>>you reach one of a set of conditions:
>>-- size of changes > some default size
>>-- user is not doing anything (cycle stealing, of a sort :-)
>>-- user goes forward or backwards in the file some distance > x
>
>>Any questions?
>
>Why, yes.  What if the text to be inserted is greater than the space on
>the disk?  There is no super-elegant way of doing this.  You'd have to
>allocate more disk space, link it in.  Sounds like a lot of
>system-dependent stuff to me.

	It shouldn't be anymore 'system-dependent' than if you try to insert
more stuff than you have Main memory for.  IE, when your I/O to disk fails,
you tell the user that "sorry mem/disk is full" and drop them OUT of insert
mode.
	If you're buffering the inserted text before writing it, then you
ought to keep track of how much disk space is available, but it you just
send it direct to disk (gets(userinput); fputs(userinput, userfile);)
then there's no problem (other than speed, and the OS will hopefully buffer
it enough to be usable).

	-- Matt

    *~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~*
    %    "I programmed three days        %      Beam me up, Scotty.      %
    %     And heard no human voices.     %     There's no Artificial     %
    %     But the hard disk sang."       %    Intelligence down here.    %
    %          -- Yoshiko                                                %
    %                            E-mail:  mrush@cscihp.ecst.csuchico.edu %
    *~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~*
     This is a SCHOOL!  Do you think they even CARE about MY opinions?!