search

neovim / neovim

Vim-fork focused on extensibility and usability
https://neovim.io
Other
82.97k stars 5.69k forks source link

} is replaced by ^_ when editing #12207

Closed nlguerra2003 closed 2 years ago

nlguerra2003 commented 4 years ago

In neovim 0.4.3 for Windows 10, whenever I type a } sign (curly brace closing), it inserts two chars: ^_ (a circunflex and an underscore) instead of inserting the desired symbol. These two symbols can be deleted in a row (only one tap on the backspace symbol deletes all two chars, and even a left arrow or right arrow tap jumps directly to the opposite side), and are not saved as printable characters (both chars are saved only as only one hex 1F symbol, invisible to most text editors).

glacambre commented 4 years ago

Can you reproduce this with neovim nightly?

If yes, what terminal/GUI are you running neovim in?

nlguerra2003 commented 4 years ago

@glacambre, nvim-qt.exe does not have this bug, as far as I am concerned. As to nvim.exe, I tried to verify if this error happened in windows terminals. From the traditional Windows command line to Windows Powershell they both show this error.

teto commented 4 years ago

Please try with nightly https://github.com/neovim/neovim/releases/tag/nightly ?

nlguerra2003 commented 4 years ago

It shows the bug as well (sorry, did not know what you meant by nightly).

justinmk commented 4 years ago

related https://github.com/neovim/neovim/issues/11061

erw7 commented 4 years ago

@Vyber90 Try NVIM 0.5.0(nightly) on the following page.

https://github.com/neovim/neovim/releases

dundargoc commented 2 years ago

I've tried neovim version 0.4.3 on windows with powershell and also had trouble inputting {}, while I had no problems on nvim-qt. Same for neovim version 0.4.4. I did not have same problem as @nlguerra2003 since the problem is dependent on keyboard language. I use Swedish which meant that { [ ] } instead became 7 8 9 0 (aka the Alt Gr key didn't work). When I switched to English keyboard I could input { [ ] } just fine. Had this issue not been almost 2 years old I'd have asked what keyboard language @nlguerra2003 is using :) . My keyboard problems went away after upgrading to neovim 0.5.0. While it's not an absolute guarantee that this is solved, it's very likely, especially considering the many accounts of neovim input working after version 0.5.x. I will therefore elect to close this.