Closed takezo39 closed 7 months ago
Hi @takezo39, I wasn't able to reproduce the issue in either my own environment or with a fresh install. To help diagnose the issue, can you please look into the following?
Hi @firai, with the help of your questions I managed to track the problem down to ~/.jupyter/lab/user-settings/@jupyterlab/shortcuts-extension/shortcuts.jupyterlab-settings
. Although I had a fresh install, these files were not fresh.
Attached you can see a vimdiff
of the regenerated version of the file after I removef it from the above location (left) vs. the old version (right). I'm not sure how it ended up like that but possibly from me messing around with key settings at some stage.
Thanks for your help. Should I close this issue?
Hi @takezo39, thanks for reporting back. We made those changes in v4.0.3 in #107. There were also additional changes to the keyboard shortcut settings in v4.1.0 from #110.
I think this was caused by the fact that JL pre-populates keyboard shortcut settings when it is first run, so the old defaults stick even if the user hasn't customized any of the keyboard shortcuts. I just filed an issue upstream at https://github.com/jupyterlab/jupyterlab/issues/15326 to propose not pre-populating, but that doesn't help users who are already using JupyterLab. I'm not sure if there's a way to better advertise these changes and the fact that the user may need to reset/check their settings. Maybe an entry in the wiki and some sort of toast message on upgrade when we do it again in the future?
Sorry for the late reply. I'm not sure myself what the best solution is. I'm not too familiar with JL. Maybe if this hasn't been an issue for others it doesn't need a fix? In any case I will close this. Feel free to reopen if this is premature.
Hi @firai, with the help of your questions I managed to track the problem down to
~/.jupyter/lab/user-settings/@jupyterlab/shortcuts-extension/shortcuts.jupyterlab-settings
. Although I had a fresh install, these files were not fresh.Attached you can see a
vimdiff
of the regenerated version of the file after I removef it from the above location (left) vs. the old version (right). I'm not sure how it ended up like that but possibly from me messing around with key settings at some stage.Thanks for your help. Should I close this issue?
hi @takezo39
I have the same problem, but I don't understand how you solved it. Did you delete the shortcut file?
@sphyrnidae8 Currently the only ways to fix the issue that I'm aware of would be to either:
Keyboard Shortcuts
settings in the Settings Editor
and click Restore to Defaults
to reset all user keyboard settings, which will remove the old conflicting settings, orJSON Settings Editor
.@sphyrnidae8 Currently the only ways to fix the issue that I'm aware of would be to either:
1. Go to `Keyboard Shortcuts` settings in the `Settings Editor` and click `Restore to Defaults` to reset all user keyboard settings, which will remove the old conflicting settings, or 2. Manually copy the latest default rules to your local settings using the `JSON Settings Editor`.
Hm, tried that already several times. Doesnt work here.
Then your issue may not be caused by the one listed here. Please file a new issue with information about your environment and steps to reproduce.
Description
Esc does not revert to normal mode after using Shift+r to replace multiple characters
Reproduce
Expected behavior
Should go into normal mode but stays in replace mode. Pressing Ctrl+c or Ctrl+[ does go into normal mode.
Context
Python package version:
Extension version: 4.1.0
Command Line Output
Web Browser Output