Undefined variable: g:evervim_color_theme about evervim HOT 4 CLOSED

NeoVim started after I did :PlugInstall in Vim. So it appears you need to install EverVim on Vim before NeoVim can use it.

Also another issue, when NeoVim started the first time and after restarting Windows, it warns that the Knack NF font has a bad pitch.

Warning: Font "Knack NF" reports bad fixed pitch metrics.

The fonts are missing the right edges in neoVim, but in Vim the font looks fine.

from evervim.

Hi @JimmyJames707 , undefined variables about color themes only occurs when you first boot up EverVim, because at that point the color theme packages have not yet been installed. And you can just hit Enter to skip that and the plugin installation should automatically begin. But from your description, I assume you did hit enter, but nothing happened, and you did try run :PlugInstall immediately after, but it still doesn't work. (Right?)

I currently don't have a Windows 7 installed, but I can try a fresh installation on my WIndows 10 environment.

As for ctags download link... The ctags project is hosted on SourceForge, which is under heavy DDoS attack in the past few days, many projects relying on their file storage service (e.g. Manjaro, MinGW, and Ctags) may encounter problems with downloading from SF.

You can just install EverVim without ctags for now. And just press 'u' on the startup screen to trigger a full upgrade after ctags is in your PATH, and tagbar feature should be automatically re-enabled.:)

from evervim.

Bug confirmed and reproducable on Windows platform. I've fixed the undefined variable, but it seems that the cause is something else. Neovim-win32 at that time is not even responding to keyboard Enter. I'll probably try a git snapshot of Neovim later (after I finished my midterms).

Right now, the problem seems undeterministic, I tried removing all the if NVIM() code and run just like what Vim would see, but it still won't pass that and refuse to start plugin installation. It may be because of some changes from neovim 0.2 to 0.2.x.

from evervim.

Hi @JimmyJames707 , this bug is caused by Neovim 0.2's incorrect handling of Windows terminal environment, and therefore echo message cannot be skipped using keyboard event. I've temporarily made an work around, which is simply disable output on the initial installation. Everything should work fine now.

For future problematic installation under Windows, there is now a Appveyor autobuild set up for downloading and precompiling the plugins for Windows. Therefore, if you don't want to spend time cloning and installing the plugin on your local machine, you can just download the bundle zip and unzip it to the .EverVim folder.

Link to the latest Windows bundle artifact is here.

from evervim.