Repository navigation
IDLE -- jump to home should not go past the PS1 and PS2 prompts #61262
Description
| BPO | 17060 |
|---|---|
| Nosy | @rhettinger, @terryjreedy, @serwy, @roseman |
| Superseder |
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
GitHub fields:
assignee = None
closed_at = <Date 2017-06-19.20:45:59.825>
created_at = <Date 2013-01-28.09:17:44.205>
labels = ['expert-IDLE', 'type-feature']
title = 'IDLE -- jump to home should not go past the PS1 and PS2 prompts'
updated_at = <Date 2017-06-19.20:45:59.823>
user = 'https://github.com/rhettinger'bugs.python.org fields:
activity = <Date 2017-06-19.20:45:59.823>
actor = 'terry.reedy'
assignee = 'none'
closed = True
closed_date = <Date 2017-06-19.20:45:59.825>
closer = 'terry.reedy'
components = ['IDLE']
creation = <Date 2013-01-28.09:17:44.205>
creator = 'rhettinger'
dependencies = []
files = []
hgrepos = []
issue_num = 17060
keywords = []
message_count = 4.0
messages = ['180841', '181155', '185883', '296373']
nosy_count = 4.0
nosy_names = ['rhettinger', 'terry.reedy', 'roger.serwy', 'markroseman']
pr_nums = []
priority = 'normal'
resolution = 'duplicate'
stage = 'resolved'
status = 'closed'
superseder = '18444'
type = 'enhancement'
url = 'https://bugs.python.org/issue17060'
versions = ['Python 2.7', 'Python 3.3', 'Python 3.4']
Activity
rhettinger commentedon Jan 28, 2013
terryjreedy commentedon Feb 2, 2013
serwy commentedon Apr 3, 2013
When using the IDLE Classic OSX key set, the "beginning-of-line" virtual event gets bound to <Control-Key-Left>. Using this key set I can repeat the behavior that Raymond observed.
The .home_callback() in Lib/idlelib/EditorWindow.py contains the logic from bpo-3851 for placing the cursor at the beginning of the prompt, but it requires that a key combination be bound to the beginning-of-line virtual event.
Should we append "<Key-Home> <Control-Key-a>" to the begining-of-line config in Lib/idlelib/config-keys.def ?
terryjreedy commentedon Jun 19, 2017
I am closing this instead of bpo-18444 because the latter has more extensive discussion.