[Gretl-users] unsaved datafile closed w/o asking

[Sven Schreiber]

Am 18.12.2007 18:41, Sven Schreiber schrieb:
> Am 18.12.2007 15:50, Allin Cottrell schrieb:
>> 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.
>>   
> 
> True. However, the possibility of dataloss as I experienced myself makes 
> me feel a bit uneasy about this. As a little safety net, couldn't the 
> 'open' command check whether the current datafile has unsaved changes, 
> and if so, create an automatic backup copy before discarding it?

I have been bitten by this again... is there anything wrong about the 
idea of automatic backups? Especially now that the workdir reforms 
should have ensured that the directory is writeable.


>> Probably a note to this effect should be added to the manual.
>>
>>   
> 
> That would also be good.

Yes I see that as a reminder to myself to eventually contribute that.

-sven