🚀 go-pugleaf

In article <MWM.90Sep26152421@raven.pa.dec.com> mwm@raven.pa.dec.com (Mike (My Watch Has Windows) Meyer) writes:
>In article <14669@cbmvax.commodore.com> andy@cbmvax.commodore.com (Andy Finkel) writes:
>Is that on the device the file is on, or on the device the text editor
>was started from? And it's sort of silly if you that device winds up
>being ram:. Likewise, you have to deal with being able to write on
>that file. Since mg isn't part of a commercial product, I'm tempted to

Its :t relative to the current directory, actually.

I'd suggest :t relative to current directory, falling back to
:t on the same volume as the source file if there's not enough
space in the first choice volume.

This neatly avoids the ram: problem, since RAM: is always 100% full.

(actually, you could also try the same volume first, falling
 back to relative to the current directory; that would work out too)

			andy


>make this feature something you have to enable at compile time, and if
>it's on, allow the user to give a file name for the disk buffer file.

That wouldn't be that bad either.

>
>	Thanx,
>	<mike

		andy
-- 
andy finkel		{uunet|rutgers|amiga}!cbmvax!andy
Commodore-Amiga, Inc.

"Nothing is as permanent as a temporary kludge."

Any expressed opinions are mine; but feel free to share.
I disclaim all responsibilities, all shapes, all sizes, all colors.