moving around cells with up/down key in "edit" mode can strand cursor

[sjobeek]

I know it's a work in progress, but just providing some feedback. Thanks a ton for working on this!

With some vigorous movement between cells using the up/down keys while in normal edit mode, I managed to "strand" an active blinking green cursor in more than one cell which was not the current active cell.

After clicking on one of these "stranded" cursors, the interface stayed in command mode, though typing would actually input text and execute commands at the same time.

[ivanov]

Thanks for the report, I've seen this as well. If anyone can get a small reproducible (or reproducible-ish) way of getting this behavior, it would help a lot in testing and fixing this bug.

[maxgillett]

I've been experiencing the same sort of bug. You can reproduce it easily if you load a notebook with more than one cell, toggle vimception through the help dropdown, and then click on each of the notebook cells.

I'll poke around in the code a bit later and see if I can figure it out. Thanks for the awesome plugin.

[RichardWarfield]

I had the same (or a very similar) problem. The issue seemed to be exceptions that were occuring (for reasons I don't entirely understand) in the "blur" handler. I think these were short circuiting the cm_all call. Adding try-catch blocks (and ignoring the exceptions) to the offending code lines seems to have fixed the problem for me. I submitted a pull request below.

#18