Now that's an interesting suggestion that had not occurred to me.  Is
there some way we could leverage this fact to avoid this sort of problem
in the future, it seems to have come up more than once already.

On the one hand perhaps the updating logic could create a new temporary
project and enter it before starting the update then exit and delete it
when the update is complete?  Alternatively could the logic do some
subset of what happens when a new project is entered but as effective
for this purpose?  On the third hand does atomic loading address this
problem more effectively and more directly?

Ken

On Thu, 2009-08-27 at 23:05 +0200, Bert Freudenberg wrote:
> Simply entering a new project before updating should work as well.
> 
> - Bert -
> 
> On 27.08.2009, at 19:10, Markus Lampert wrote:
> 
> > I have indeed one text window open. I'm hesitant to close it though  
> > since I did some manual formatting in the file and would hate to  
> > have to do that again. Is there a way to maintain the formatting  
> > over saving and reading again?
> >
> > Thanks for all the pointers!
> >
> > Have fun,
> > Markus

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20090827/9168e154/attachment.pgp