-
Notifications
You must be signed in to change notification settings - Fork 104
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
mintty sends a ctrl+x when opening vim? #55
Comments
Please provide a terminal log of the incident. Add options Log=filename and Logging=no to the config file, then before starting vim enable logging (from Ctrl+right-click context menu), and stop it right after the incident. |
Closing this because so far Vim has found a source of the problem. I have another similar bug I will try to see if goes away on the same commit. |
I see no Ctrl+X in the log. Does vim react to Ctrl+X in a specific way? If yes, how and at which position, so I can see what happens in the log before? |
Normal behaviour: Cursor lands on char before HostName.
What happens: CTRL+X increments next number so it jumps to 46 in this case
and decrements to 45.
|
This isn't really helpful. I see multiple strings "HostName" and no 45 or 46 in your log. As I'm not a vim user myself, I also don't reproduce your issue. Some more specific analysis is required to be able to assess this issue, relating to pure terminal interaction. Please find out on which event you think mintty sends anything inappropriate (which I doubt). Otherwise I can only close the issue, sorry. |
Closing this for missing evidence. |
Released 1.8.0. |
I am gonna link the original issue:
vim/vim#2003
This only happens with newer versions of Vim not 7.4 from Debian/Ubuntu repo.
I have tried on phone and on PC and the only where I can reproduce consistently is within mintty.
My terminal-emulator implementation knowledge is limited however so that's where I hope you can help me debug this bug - which seems to have something to do with a translation of the vim normal command
g'"
in mintty.I tested in latest putty as well that doesn't have this issue.
The text was updated successfully, but these errors were encountered: