This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author terry.reedy
Recipients roger.serwy, terry.reedy
Date 2011-10-15.01:12:37
SpamBayes Score 1.1979751e-11
Marked as misclassified No
Message-id <1318641158.22.0.196333428254.issue13179@psf.upfronthosting.co.za>
In-reply-to
Content
This is more of a feature request than a bug report, in that the behavior appear intentional. But that is a moot point in that new IDLE features do not have to wait for a new release. The proposed new behavior seems plausibly better. I just wonder if anything in flist.vars *should* carry over (maybe as a copy) to all edit windows, but I do not know its contents.

Also, I can imagine that someone who knows about (I did not before) and likes the 'code context' option (I might start using it) would want it to be always on once turned on. That suggests that it should be added to the configure dialog before being made local with this patch. I might feel the same about at least some of the other vars also.
History
Date User Action Args
2011-10-15 01:12:38terry.reedysetrecipients: + terry.reedy, roger.serwy
2011-10-15 01:12:38terry.reedysetmessageid: <1318641158.22.0.196333428254.issue13179@psf.upfronthosting.co.za>
2011-10-15 01:12:37terry.reedylinkissue13179 messages
2011-10-15 01:12:37terry.reedycreate