forked from git/git
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Vim not accepting capital letters and control-keys #2689
Milestone
Comments
Does this still happen with the latest snapshot? (I ask because MinTTY and MSYS2 runtime were upgraded in that snapshot.) |
indeed it fixes the issue. closing then. |
Excellent! |
dscho
added a commit
to git-for-windows/build-extra
that referenced
this issue
Jun 17, 2020
When pseudo console support is enabled, [the VIM editor sometimes had troubles accepting certain keystrokes](git-for-windows/git#2689), which was fixed. Signed-off-by: Johannes Schindelin <[email protected]>
Happy to report that this snapshot also fixes a couple of other |
This was referenced Jul 6, 2020
1 task
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Setup
defaults?
to the issue you're seeing?
I don't know
Details
mintty 3.1.6
Minimal, Complete, and Verifiable example
this will help us understand the issue.
I am not exactly sure this is the right place to report it. However I only notice the problem when writing my commit message (e.g. when git calls Vim). When starting vim normally, I do not see this problem (and yes, I checked
:version
output, it is using the same vim every time).The thing is, I cannot enter/type upper case letters or Ctrl-keys (neither in insert mode nor as commands), which kind of limits my ability to write commit messages or navigate around :/
Some letters still work, like
!
or:
(which require me to press shift). It looks like Vim is never receiving the keys.This might as well be a Vim bug, however I cannot reproduce by running
vim
from within git-bash. I also spend some time chasing my option settings and configuration, to see if this is caused by it. While I see some differences, neither of them seems to cause this issue. So not sure.I see that the default $TERM for mintty is
xterm-256color
and that's also what:set term?
returns. So as a blind guess, I did:set term=builtin_vt320
and I still have colors available and upper case letters seem to work again.Since Vim has been implementing xtermModifyOtherKeys (https://invisible-island.net/xterm/modified-keys.html) in the late 8.2 versions, I suspect, that Vim is somehow confused about the terminal capabilities and if I add those lines to /etc/vimrc to disable the modify-other-key feature of Vim:
" disable xterm modifyOtherKeys
let &t_TI=''
let &t_TE=''
Vim works flawless as my commit editor again. It might be advisable to add those lines to /etc/vimrc in any case, since I suspect it is quite unlikely, that mintty will support xterms modify-other-key feature anytime soon.
I suppose an update to the Vim package could also fix it, there were quite some patches and bugfixes around this particular feature recently (and also how vim is detecting a true xterm terminal).
Keyboard layout and locale of Windows is German.
For the record, this is the output of
:version
:The text was updated successfully, but these errors were encountered: