[issue22707] Idle: changed options should take effect immediately

Terry J. Reedy added the comment: Turning extensions into features #27099 fixed many (all?) unnecessary delays but a few things should be checked, and the help texts reviewed. -- versions: +Python 3.8 -Python 2.7, Python 3.4, Python 3.5 ___ Python

[issue22707] Idle: changed options should take effect immediately

Terry J. Reedy added the comment: I looked at the how the num_spaces and current General options are defined, set, and updated. editor-on-startup: local name in pyshell.main. width, height: used in text_options, passed to MultiCallCreator(Text). (Width is EW() attribute, initialized in EW.__i

[issue22707] Idle: changed options should take effect immediately

Terry J. Reedy added the comment: To expand on the initial statement, changes can take effect a) when IDLE start (the initial window option), b) when a new editor window is created (the initial size option), c) immediately for all editors (indent size and most others), and d) immediately for t

[issue22707] Idle: changed options should take effect immediately

Terry J. Reedy added the comment: For Idle preferences, a Help text could list options that do not take effect immediately. For extensions, there should be an indication in an extension's option-help (#22705). -- ___ Python tracker

[issue22707] Idle: changed options should take effect immediately

Changes by Terry J. Reedy : -- versions: +Python 2.7, Python 3.4, Python 3.5 ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue22707] Idle: changed options should take effect immediately

New submission from Terry J. Reedy: Currently, some option changes take effect immediately, and some only when Idle is started again. To the extent possible, options should take effect immediately, perhaps by not caching values outside of the config dictionary that records changes before they