Skip to content

[DO NOT MERGE]: maybe fix crossed keybindings in ipython 4.1 #6053

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

Closed
wants to merge 2 commits into from

Conversation

tacaswell
Copy link
Member

Possibly fixes jupyter/notebook#949

attn @ericdill

@tacaswell tacaswell added this to the unassigned milestone Feb 23, 2016
@tacaswell tacaswell changed the title FIX: maybe fix crossed keybindings in ipython 4.1 [DO NOT MERGE]: maybe fix crossed keybindings in ipython 4.1 Feb 23, 2016
@tacaswell
Copy link
Member Author

This 'fixes' the jupyter problem by removing all the interaction with the jupyter keyboard manager.

attn @Carreau

@Carreau
Copy link
Contributor

Carreau commented Feb 23, 2016

Ping @takluyver, @minrk and @jdfreder I'll try to have a look, but that will be hard in the next few days. @parleur you recently looked at the keyboard shortcut for vim/emacs/sublime keybindings.

@tacaswell
Copy link
Member Author

Any progress on this? Does the new widget fix this?

@jenshnielsen
Copy link
Member

I believe it's fixed by the new widget but it would be good to fix this on 1.5.x/2.x too

@tacaswell
Copy link
Member Author

Do we have any idea what the underlying problem is? I am not even sure if this needs to be fixed on our side or the jupyter side.

@tacaswell
Copy link
Member Author

@Carreau Did you make any progress on this from the ipython side?

@tacaswell
Copy link
Member Author

replaced by #6752

@tacaswell tacaswell deleted the fix_js_nbagg_focus branch July 19, 2016 16:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants