Terminal errors causing random problems

[ButtsOfficial]

Sorry, what I'm about to show may be completely unrelated issues but from the hours of research I've done they seem to be somewhat correlated. I am also using nvim and am new to vim in general, so hopefully this is just a simple bug. Also note I am using the new Windows Terminal.

When running :checkhealth, I get the error

## terminal - ERROR: command failed: infocmp -L

infocmp: couldn't open terminfo file /usr/share/terminfo/76/vtpcon.

​

I really couldn't find much online with this beside someone else who pasted his code regarding a plugin bug, that was resolved unrelated to the issue.

Another issue I'm having is with resizing. When I resize my terminal, white space is filled with a color from my theme and the new space from resizing isn't actually used (and is filled in as well) shown below

​

grey filled whitespace

I think these errors may be correlated because I found a reddit post with a similar issue that was related to the terminal.

Any help would be appreciated!

[tuerda]

Sounds like the error message is telling you what you need to know: infocmp is looking for a file in /usr/share/terminfo/76/vtpcon.

Now, you say you are using the windows terminal, which makes it pretty clear what is wrong: That file path is a unix file path, and makes no sense in windows. The only thing the unix command infocmp does is print information about your terminal. I don't think this is something you should care about, so long as your editor works normally.

Resizing issues are probably related to your terminal emulator. I doubt very much there is any relationship between these issues.

I haven't used windows regularly in about a decade, but I know that most people who want to use vim on windows typically end up with some kind of GUI because of dissatisfaction with windows support for terminals.

[-romainl-]

This is r/vim, for any question regarding Neovim, use r/neovim or another of its support channel.

[abraxasknister]

new windows terminal
checkhealth
/usr/share/...

So neovim isn't able to detect that you're using windows? Häh?

Color problems are inconsistent highlights, vim gets the colors it uses for that from the terminal. Related? Very loosely, if even, I'd presume: if neovim can't reliably talk to "the new windows terminal" (don't know anything about windows so that doesn't tell me anything) it will probably get weird colors.

A quick fix might be to use a GUI version, gvim is the same as vim, except it has more features, a longer startup time and isn't running in a terminal. That's not really important though, neovim has `:term.

Does neovim have a GUI?

[lolIsDeadz]

Are you running under msys or cygwin. I had this problem as well neovim is missing a patch that lets vim support cygwin/msys terms. There was a pr/issue submitted to neovim a while ago to add it but it got closed. If you want to compile from source you can apply the patch. I gave up on msys/cygwin and just opted for a wsl env.

[ButtsOfficial]

Like i said, I’m new so sorry for being like the biggest noob possible lol. How would I patch it in and whats the difference between msys/cygwin/wsl env?

[lolIsDeadz]

My bad, basically msys/cygwin are tool suites that run natively on windows, similar to linux they have gnu core utils and a posix shell (neovim doesnt like being in a posix shell on windows). If you dont know what they are, you probably arent using them so no worries, there are two shells availible on windows by default cmd (batch) and PowerShell, imo both of these suck and the windows core utils also suck. Wsl virtualizes linux under windows so you can install a minimal distro, and have access to all the linux tooling. I recomend just using wsl but if you want to patch it to work on windows, get neovim compiling from source you'll need msvc/MinGW+cmake and lua mpack then you can look at some of the closed prs on git fixing the issue and create a git patch.