Thanks for clearing up my misunderstanding about the shell window coming forward. Some years ago that wasn't the case and was one of the reasons for VIDLE.
We agree that "No prompt" should be the default for Autosave Preferences/At Start of Run once a file exists, but we disagree on the value of being able to test a few lines of code without there having to be a file. Yes, one can of course create a test.py file somewhere for such uses, and get to it through Recent Files. But I don't like being a second-class citizen in this regard. Those who prefer to do their testing in the shell window are not required to create and/or open a file for the purpose, and if I choose to run complete routines from the edit window I shouldn't have to do this either. I want to be able to use the editor the way others use the shell, with the same immediacy. Hence my strong desire for the option "If file has never been saved, No prompt". On the other hand, we judged it prudent to specify for occasional users (our intro physics students) "If file has never been saved, Prompt to Save", to make sure that they've saved the file to a permanent place even if there is a crash during the session. Hence the extra options implemented by Polo. We want and need the flexibility to tailor the environment. At the end of Polo's 2009 project, I thought there was agreement that his changes were acceptable. I agree that in addition to the autosave that occurs on a run, it would be good to implement timed backups and/or other mechanisms for guarding against crashes. Bruce
_______________________________________________ IDLE-dev mailing list [email protected] https://mail.python.org/mailman/listinfo/idle-dev
