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

With vscode-neovim, sometimes causes duplicate text to appear upon exiting insert mode #376

Open
BlueDrink9 opened this issue Jan 13, 2025 · 0 comments
Labels

Comments

@BlueDrink9
Copy link

Explain the issue

I don't have time to do minimal reproduction or thorough diagnosis, but I'm opening this here so that if other people have a similar issue, they can discover that matchup might be causing it. I hope you don't mind. I suspect it's a complicated interplay between vscode's completion, matchup, and maybe some of the other settings I have.
Possibly related to #325

After using VSCode-neovim for awhile, especially after completing a workspace function suggestion, exiting in certain mode seems to input a second copy of anything that was just inserted.

  1. What vim version are you using? If using neovim, Are you using
    tree-sitter or classic matching?
    treesitter, nvim 10.1
  2. Steps to reproduce
    -- NA for now
  3. Expected behavior
  4. Observed behavior

If your issue is instead a feature request or anything else, please
consider if minimal examples and vimrc files might still be relevant.

Minimal working example

Please provide a minimal working example, e.g.,

if l:x == 1
  call one()
elseif l:x == 2
  call two()
else
  call three()
endif

Minimal vimrc file

Please provide a minimal vimrc file that reproduces the issue. The
following should often suffice:

set nocompatible

" load match-up
let &rtp  = '~/.vim/bundle/vim-matchup,' . &rtp
let &rtp .= ',~/.vim/bundle/vim-matchup/after'

" load other plugins, if necessary
" let &rtp = '~/path/to/other/plugin,' . &rtp

filetype plugin indent on
syntax enable

" match-up options go here
@BlueDrink9 BlueDrink9 added the bug label Jan 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant