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.

Title: Idle extension configuration and key bindings
Type: enhancement Stage: patch review
Components: IDLE Versions: Python 3.8
Status: open Resolution:
Dependencies: Superseder:
Assigned To: Nosy List: Saimadhav.Heblikar, terry.reedy
Priority: normal Keywords: patch

Created on 2014-10-23 00:17 by terry.reedy, last changed 2022-04-11 14:58 by admin.

File name Uploaded Description Edit
issue22706_1.diff Saimadhav.Heblikar, 2014-12-28 08:01 review
Messages (5)
msg229848 - (view) Author: Terry J. Reedy (terry.reedy) * (Python committer) Date: 2014-10-23 00:17
In default config-extensions.def, section [X] is followed by section [X_cfgBindings]. In user config-extensions.cfg, the two sections are written independently by the config dialog (key bindings) and by the extensions dialog (the [X]).  While having [X] and [X_cfgBindings] separated and even reversed in order seems to still work, it would be nicer if they were written together in the proper order.  It might be possible to do this in the user-config writing method in config-handler.
msg232654 - (view) Author: Saimadhav Heblikar (Saimadhav.Heblikar) * Date: 2014-12-15 10:08
Need some clarification on this issue. I tried changing the cfgBindings for FormatParagraph. It creates a new key-set and writes the changes to user config-keys.cfg in ~/.idlerc(the keybindings). Any changes made to FormatParagraph in extension dialog(the [X]) are written to the user config-extensions.cfg file in ~/.idlerc.

Have I understood the issue correctly in saying that the desired outcome is both [X] and [X_cfgBindings] write to config-extensions.cfg in ~/.idlerc?
msg232717 - (view) Author: Terry J. Reedy (terry.reedy) * (Python committer) Date: 2014-12-16 07:11
When I alter an *extension* key binding (in the keys page of idle pref dialog), the change shows up in .idlerc/config-extensions.cfg, not config-keys.cfg.  For instance,

zoom-height = <Control-Alt-Key-space>

If I also disable zoom-height, the following appears in a separate part of the same file.


For me, the two blocks are already in the same file.  The same is true for FormatParagraph.  I intended this issue to be about bringing them together in the file, with the [X] block first.  You seem to be saying that the current behavior is different on linux.  Since FormatParagraph is still special (see #20577), try ZoomHeight also.
msg232810 - (view) Author: Saimadhav Heblikar (Saimadhav.Heblikar) * Date: 2014-12-17 08:00
ZoomHeight behavior on linux is as what you mentioned. Now I have understood this issue. Working on it.
msg336164 - (view) Author: Terry J. Reedy (terry.reedy) * (Python committer) Date: 2019-02-21 00:30
#27099 (converting built-in extensions to features) made this less important.  But it is still relevant to actual extensions.  There is a dummy extension, zzdummy, for testing.
Date User Action Args
2022-04-11 14:58:09adminsetgithub: 66895
2019-02-21 00:30:26terry.reedysetstage: needs patch -> patch review
messages: + msg336164
versions: + Python 3.8, - Python 2.7, Python 3.4, Python 3.5
2014-12-28 08:01:44Saimadhav.Heblikarsetfiles: + issue22706_1.diff
keywords: + patch
2014-12-17 08:00:24Saimadhav.Heblikarsetmessages: + msg232810
2014-12-16 07:11:57terry.reedysetmessages: + msg232717
2014-12-15 10:08:41Saimadhav.Heblikarsetmessages: + msg232654
2014-10-31 17:44:44Saimadhav.Heblikarsetnosy: + Saimadhav.Heblikar
2014-10-23 00:17:33terry.reedycreate