-
Notifications
You must be signed in to change notification settings - Fork 37
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
Opening vim shows an empty screen (with the file name at the bottom) #69
Comments
The commit causing this appears to be a205930 |
I pushed a fix directly to The current status is now part way between the original and the new - it only makes a new buffer when required, but also avoids corrupting Please let me know what you think @figuerom16 |
That's really strange. I'm trying to replicate the problem in PopOS opening vim, but I can't seem to recreate the issue.
The only other error I'm getting is Is there a way I can recreate the vim issue easily? |
Found a way to disable the previous error. It's a special escape sequence that vim uses. >4;2m
I don't know if this was causing any issues with your vim though. EDIT: thinking about this more if >4 is throwing an error then 2m gets processed. Wouldn't that mean that vims color mode gets set to Dim/Faint mode? Nevermind color mode 2 isn't being handled so it shouldn't cause an issue. |
Just to confirm I tested this and the warnings did go away but the error with not loading content in vim remains. |
A regression in the last month has somehow stopped vim from working on my Linux computer.
Cause was PR #64
The text was updated successfully, but these errors were encountered: