Re: Flushing the delete buffer (WAS: pgm leaks code into text)

[TBaehr TBaehr@xxxxxxxx]

Bravo, Wolfie!

When you mentioned the RAM disk, I remembered another trick: I had Xy3 set up
so that, if I hit the hot key to start a CI command ("Change Invisible"), a
little XPL program saved the current file to a scratch file in the RAM disk.
Since CI is not always reversible, this ploy forced my system to save the last
state just before a big change. I had another key that would kill the current
file and call the RAM scratch file back under the original name. The whole
thing was a one-level Undo for improvident search-and-replace events.

As with Wolfie's trick, the RAM conveniently (for me, anyway) went away at the
end of the Xy session. Since at the time I was running under DOS, I didn't
have to worry about GPFs.

Tim Baehr
tbaehr@xxxxxxxx