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
Fixed Multicursor backspacing #7401
Conversation
Thanks for making a pull request to JupyterLab! To try out this branch on binder, follow this link: |
Thanks @bthayer2365! I don't have a working laptop at the moment to test but this logic looks great to me! |
Great, looking forward to you testing it! |
Very nice! This is identical to the behavior I see in VS Code. I think these build errors were temporary, kicking the builds. |
Linux integrity errors:
I fixed all the var/let issues. Changing var to let for Windows JS error:
I don't know how to interpret these. Maybe changing things from var to let will clear that up, but if not, could you let me know what to do? The Linux Docs error doesn't seem to be my fault, so I'm leaving it as is. |
The error you saw is being tracked in #6415. Yes, the docs failure is temporary until we release 1.2. Thanks again, and congratulations on your first contribution to JupyterLab! |
@blink1073 - should this be backported to 1.2? |
@meeseeksdev backport to 1.x |
…1-on-1.x Backport PR #7401 on branch 1.x (Fixed Multicursor backspacing)
References
fixes #7205
Other references:
jupyter/notebook#4880
jupyter/notebook#4796
Code changes
Iterates through selections, and handle backspacing appropriately. There are three cases:
3. Can be broken down into the cases of the beginning of the line too, but they behave as you would expect
This solution is similar but not exactly the same as for the same problem in jupyter notebook jupyter/notebook#4880
User-facing changes
Basically, backspacing when using multicursor works as expected now whereas before it didn't handle tabs correctly.
Backwards-incompatible changes
None