Chris writes: > >Usually BBEdit prompts you to save changes. > > Only if the changes were made in BBEdit. BBEdit reasonably > thinks that it has write control over the file. Actually, I would say this is not reasonable behavior for an application running in an operating system capable of context switching on-the-fly between concurrent applications. I think reasonably astute users would expect files to ONLY be written in a save operation. I think I'd be pretty pissed off if, for instance, I created a file in BBEdit and saved it. Forgot to close the window. Then executed a MacPerl script that appended or otherwise modified the file. Then went back to BBEdit to look at the changes. Realized that I had not closed the window and needed to reload the file. Closed the window. Reopened the file and found that BBEdit had automatically erased everything I did since my original save operation... Actually, I'd be totally confused as to why my script didn't run at first... THEN I'd be pissed that I had to waste my time debugging a non problem! >From what SeanC describes, this sounds like a plausible and not too unlikely scenario. jay ***** Want to unsubscribe from this list? ***** Send mail with body "unsubscribe" to mac-perl-request@iis.ee.ethz.ch