Re: Re-opening files

[Robert Holmgren holmgren@xxxxxxxx]

To TimBaehr:

Just saw yr msg of 10-12-95 _re_: "Re-opening files"

So, what you do is set Command Override=On? VA$OO=1? Then you
redefine fundamental commands like CAll, EDit, NEw, REad, check
whether they succeed, and if so append the filename to a list in
a S/G###? ReCAll them from a list box @VA### in a DLG frame?

Hmmm. It makes me uneasy to redefine the operation of the most
basic commands in EDITOR. I think it's bad policy. Override_On
seems like something permissible in private (personal)
programming, but not in public programming, because it burdens
users with non-standard systems that they don't understand &
can't fix or manipulate when the idea wears out, while
simultaneously depriving them of the standard issue.

I'd go another, simpler route. You want this info to survive a
shutdown; the whole point (it seems to me) is to return to your
file placemarks tomorrow morning, or next week. So I'd dedicate
KBD keys to enhanced ABort and STore operations. I'd attach a PM
that logs (on disk) the filename, date, time, , and whatever
else you want (Distefano wrote something, I always forget the
name, "exempli gratia" or something, that literally restores the
total environment down to your screen colors, view mode, etc --
you could call his routine as a sub). The PM could flush
references in the disk file older than N days. Finished.
Simple.

What we need in XPL is a determined movement toward modular
programming with some agreement on the ground rules . . . We all
keep doing the same work over and over.

=======
Robert J. Holmgren holmgren@xxxxxxxx <<<< NEW address
=======            ===