On Tue, 18 Dec 2007, Sven Schreiber wrote:
not sure if this is new (probably not): with the latest windows
snapshot it seems that running the 'open' command in a script
closes the current datafile without asking the user even if the
file has unsaved changes. I find this problematic because it has
just caused me some (minor) dataloss.
No, I don't think this is new. And it would be problematic to
change this behavior, IMO.
A common (for me, anyway) cycle is: open script (which contains an
'open' command); run script (may generate new variables); inspect
output; revise script; run script again. I would find it very
tedious to be prompted for a data save each time round.
Probably a note to this effect should be added to the manual.
Allin.