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

Double ESC Needed to Escape Insert Mode after Completion Starts #264

Open
despdx opened this issue Feb 1, 2024 · 2 comments
Open

Double ESC Needed to Escape Insert Mode after Completion Starts #264

despdx opened this issue Feb 1, 2024 · 2 comments

Comments

@despdx
Copy link

despdx commented Feb 1, 2024

  • nvim --version: 0.9.4
  • terminal emulator and version: Windows Terminal 1.18.3181.0
  • Operating system/version: Linux RH205-24590 5.15.133.1-microsoft-standard-WSL2 Fullscreen support? #1 SMP Thu Oct 5 21:02:42 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
  • Have you read and followed all steps in the doc: Yes
  • Output of command set runtimepath:
runtimepath=~/.config/nvim,~/.local/share/nvim/site,~/.local/share/nvim/lazy/lazy.nvim,~/.local/share/nvim/lazy/vim-sandwich,~/.local/share/nvim/lazy/nvim-web-devicons,~/.local/share/nvim/lazy/vim-highlight
url,~/.local/share/nvim/lazy/nvim-notify,~/.local/share/nvim/lazy/hop.nvim,~/.local/share/nvim/lazy/targ
ets.vim,~/.local/share/nvim/lazy/indent-blankline.nvim,~/.local/share/nvim/lazy/vim-swap,~/.local/share/
nvim/lazy/unicode.vim,~/.local/share/nvim/lazy/whitespace.nvim,~/.local/share/nvim/lazy/which-key.nvim,~
/.local/share/nvim/lazy/lualine.nvim,~/.local/share/nvim/lazy/vim-indent-object,~/.local/share/nvim/lazy
/vim-repeat,~/.local/share/nvim/lazy/cmp-nvim-ultisnips,~/.local/share/nvim/lazy/cmp-emoji,~/.local/shar
e/nvim/lazy/cmp-omni,~/.local/share/nvim/lazy/cmp-buffer,~/.local/share/nvim/lazy/cmp-path,~/.local/shar
e/nvim/lazy/lspkind-nvim,~/.local/share/nvim/lazy/cmp-nvim-lsp,~/.local/share/nvim/lazy/nvim-cmp,~/.loca
l/share/nvim/lazy/vim-commentary,~/.local/share/nvim/lazy/fidget.nvim,~/.local/share/nvim/lazy/gitlinker
.nvim,~/.local/share/nvim/lazy/vim-fugitive,~/.local/share/nvim/lazy/bufferline.nvim,~/.local/share/nvim
/lazy/everforest,~/.local/share/nvim/lazy/gitsigns.nvim,~/.local/share/nvim/lazy/plenary.nvim,~/.local/s
hare/nvim/lazy/dressing.nvim,~/.local/share/nvim/lazy/dashboard-nvim,~/.local/share/nvim/lazy/wilder.nvi
m,~/.local/share/nvim/lazy/diffview.nvim,/tmp/.mount_nvimV33jp7/usr/share/nvim/runtime,/tmp/.mount_nvimV
33jp7/usr/lib/nvim,~/.local/share/nvim/lazy/vim-sandwich/after,~/.local/share/nvim/lazy/indent-blankline
.nvim/after,~/.local/share/nvim/lazy/cmp-nvim-ultisnips/after,~/.local/share/nvim/lazy/cmp-emoji/after,~
/.local/share/nvim/lazy/cmp-omni/after,~/.local/share/nvim/lazy/cmp-buffer/after,~/.local/share/nvim/laz
y/cmp-path/after,~/.local/share/nvim/lazy/cmp-nvim-lsp/after,~/.local/share/nvim/lazy/everforest/after,~
/.config/nvim/after,~/.local/state/nvim/lazy/readme

Describe the bug

I immediately noticed after installing this configuration into an empty .config/nvim that exiting insert mode doesn't work as expected. This is highly abnormal, but I can't see anyone who reported it before. Doesn't this bug you?

Steps to reproduce the issue:

  1. new file
  2. type `hello' followed by a newline/CR
  3. on the next line, start typing `he', the completion kicks in, but it takes two ESC to get back to normal mode.

Expected behavior
It should always take one ESC to get back to normal mode from insert mode.

I believe I had this problem in the past with another completion system. Deoplete, maybe? Anyway, others had solved the problem and I found their solution, but I have no idea what is causing it this time. Just hoping you know.

@despdx
Copy link
Author

despdx commented Feb 1, 2024

Also, it takes two CRs at the end of a line if the last token is also a partial match. This doesn't seem right at all.

@malarahfelipe
Copy link

up 👍

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