[issue22703] Idle Code Context: separate changing current and future editors

Terry J. Reedy added the comment: An experienced non-CS computer user I asked does not like 'toggle x' or 'switch x', but would like whichever of 'show x' and 'hide x' is appropriate (rather than both). For breakpoints, this would mean one menu entry, either 'set breakpoint' or 'clear breakp

[issue22703] Idle Code Context: separate changing current and future editors

Terry J. Reedy added the comment: Cheryl, you are right. The extension-feature conversion made this issue mostly obsolete. Editors start without code context and the menu only toggles the current window. If I had thought about it, I would have closed this or added an update last fall. And

[issue22703] Idle Code Context: separate changing current and future editors

Terry J. Reedy added the comment: [In #33610, msg317601, Cheryl Sabella wrote, copying here:] I've started looking at #22703, more specifically, I've been trying to recreate it. Since the config changes in 3.6/3.7 where the flag was removed from config dialog, the code context needs to be tu

[issue22703] Idle Code Context: separate changing current and future editors

Changes by Terry J. Reedy : -- versions: +Python 3.6, Python 3.7 -Python 2.7, Python 3.4, Python 3.5 ___ Python tracker ___ ___ Pytho

[issue22703] Idle Code Context: separate changing current and future editors

New submission from Terry J. Reedy: #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