You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
assignee='https://github.com/terryjreedy'closed_at=Nonecreated_at=<Date2016-09-12.07:03:30.950>labels= ['3.8', 'expert-IDLE', 'type-bug', '3.7']
title='IDLE: document all key bindings, add menu items for more.'updated_at=<Date2018-12-28.20:29:46.499>user='https://github.com/terryjreedy'
(Follow-up to bpo-15308, which added ^C Interrupt Execution to doc and Shell menu, and to bpo-27120, which proposed to add ^/ Toggle Highlighting, until I realized that that should be part of bpo-6858, about highlighting non-.py files.)
Every IDLE function should be documented. More should be on menu. Perhaps add Move/delete menus for cursor movement and directional deletion, if not a diagram.
Another idea. A searchable current key binding list, possible sortable by key as well as function. It should include fixed builtin bindings as well as extension bindings. See bpo-27120 for motivation.
Side issue 1: Menu entries for extensions do not reflect customization (? verify, from Roger).
Not erasing output/history is a feature: some shells save and restore recent history when close and open. Shell restart is an alternative to that. I fairly often replay statements after restart.
I think turning off cycling is feature bloat. (I never do so for search.)
The one history feature that multiple people have asked for, on another issue, is retrieval with up/down arrow, as seems to be standard. I now agree.
For items going under edit, which is already 'full', submenus will be needed. Since history is Shell only, separate entries are ok, at least for now, instead of 'History' and a submenu with 'previous' and 'next'.