Skip to content
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

Undo/redo broke between 0.6.5 and 0.6.11 #1445

Closed
soyuka opened this issue Mar 28, 2017 · 3 comments
Closed

Undo/redo broke between 0.6.5 and 0.6.11 #1445

soyuka opened this issue Mar 28, 2017 · 3 comments

Comments

@soyuka
Copy link

soyuka commented Mar 28, 2017

Please thumbs-up 👍 this issue if it personally affects you! You can do this by clicking on the emoji-face on the top right of this post. Issues with more thumbs-up will be prioritized.


Sadly I'm not sure what version I had before the last update (I think it was 0.6.5), I'm now running on 0.6.11. Note that this update broke my capslock binding (overriden through xmodmap) and I had to add:

    {
       "key": "capslock", "command": "extension.vim_escape"
    },

Now, I'm using the following bindings to switch between tabs:

    {
        "key": "shift+h",
        "command": "workbench.action.previousEditorInGroup",
        "when": "editorTextFocus && vim.mode == 'Normal' && !inDebugRepl"
    },
    {
        "key": "shift+l",
        "command": "workbench.action.nextEditorInGroup",
        "when": "editorTextFocus && vim.mode == 'Normal' && !inDebugRepl"
    },

Now, undo/redo is working fine until I change the tab.

I know that this looks like #977, but if I use the non-vim keybindings (ie ctrl+z), I'm able to undo!

  • VSCode Version: code-insiders_1.11.0-1490704208_amd64
  • VsCodeVim Version: 0.6.11
  • OS: debian jessie
@johnfn
Copy link
Member

johnfn commented Mar 28, 2017

How exactly does undo/redo break?

@soyuka
Copy link
Author

soyuka commented Mar 28, 2017

I was able to undo/redo after changing tabs before.

@soyuka
Copy link
Author

soyuka commented Mar 29, 2017

Okay definitely related to vscode-insiders. I switched to code-1.10 and no issues. Will open an issue there ;).

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

No branches or pull requests

2 participants