New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create IDLE Modern Mac keyset #76942
Comments
The default keymap for Cntl-A should be <beginning-of-line>, the same as Cntl-KeyLeft. This is consistent with how Cntl-A behaves at the bash prompt and in Emacs. >>> print('Hello World')
^--- Cntl-A should take you here
^------- Cntl-A currently takes you here (which is never helpful). |
That's interesting. I've always thought of Control+A to be 'select all'. https://en.wikipedia.org/wiki/Table_of_keyboard_shortcuts Do you think a new keybinding theme should be added for bash/emacs? I don't know how well emacs would work without allowing combinations like Control+X, Control-F. |
Mac key bindings and Shell home method behavior are separate and long-standing issues. They were discussed together in bpo-18444, and this could be considered a duplicate thereof. However, the two issues need to be discussed and solved separately.
Here are the beginning-of-line and select-all bindings in the various keysets. From idlelib/config-keys.def [IDLE Classic Unix] [IDLE Modern Unix] # default on *nix, design by Serhiy Storchaka [IDLE Classic Mac] # so obsolete that it almost should be removed? [IDLE Classic OSX] I am guessing that Raymond is using a Mac and a customized version of IDLE Classic OSX with Control-Key-A added as either *a* or *the* binding of the <<beginning-of-line pseudoevent. On bpo-18444, I asked whether we should make this addition config-key.def. (No answer there.) I now realize that doing so would break any custom keyset that binds ^A to any other pseudoevent. So I would be very reluctant to change the current keyset. On the same issue, Ned suggested (July 2013) that even the OSX keyset had multiple problems and should be replaced. A new keyset would have to be justified by more than one change, but would not be encumbered by back compatibility. Are standards stable enough on Mac to make a new keyset appropriate now? In June 2016, Serhiy Storchaka posted a new keyset for Linux that he claimed followed current Linux standards, such as they are. It is now the default on Linux. I would do the same for Mac if Ned and Raymond agreed on something. I changed the title of this issue to this generalization, rather than close it as a duplicate.
The underlying issue is the mixing of a read-only prompt and the first line of a possibly multiline read-write Python statement in the Shell text widget. This also leads to the indent problem and a couple of other minor issues. In retrospect, I consider this mixing a design mistake and I am working on a suggestion about fixing it. |
Terry, it would be better to get opinions from others who really use IDLE on macOS. But, FWIW:
|
bpo-18444 is about revising macOS keysets and/or making a new one. This is about the latter. So closing as duplicate. |
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:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: