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 terry.reedy
Date 2014-10-23.00:16:53
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1414023415.32.0.701318253357.issue22703@psf.upfronthosting.co.za>
In-reply-to
Content
#17535, msg225416, 2014-08-16 17:18 describes the current double behavior of Options / Code context.  It toggles the code-context state of both the current editor and the default for future editors.  The two toggles can be in opposite directions.  The check mark absent or present somewhat surprisingly indicates the initial state of future windows, not of the current window.

The consensus seemed to be that we should change to having Code Context toggle the current window only, with the checkmark indicating its current state.  The default for future windows will be left to the extension configuration, which will be easy to change with the new dialog, #3068.
History
Date User Action Args
2014-10-23 00:16:55terry.reedysetrecipients: + terry.reedy
2014-10-23 00:16:55terry.reedysetmessageid: <1414023415.32.0.701318253357.issue22703@psf.upfronthosting.co.za>
2014-10-23 00:16:54terry.reedylinkissue22703 messages
2014-10-23 00:16:53terry.reedycreate