You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running neovim-gtk with 0.9.4 or nightly installed, with the below .vimrc (tested using nvim-gtk -- -u FILE), Neovim fails to initialize with the error messages below. Note that this problem does not occur with 0.7.2. I don't believe the font is relevant; using monospace:h12 triggers the problem just as well.
I believe the problem is related to the fact that the newer versions set gui_running. I use a .vimrc that's shared between Vim and Neovim, so I used to have a branch for gvim (has("gui_running")) which simply called my SetGUIOptions function, and a branch for Neovim which did that on UIEnter.
Obviously I can change the order, but it seems less than ideal for neovim-gtk to hang when Guifont is invoked during startup. I should note that Neovim-Qt with 0.9.4 simply complains about the lack of Guifont, so it doesn't appear that this is an intrinsic limitation of newer versions of Neovim. If this isn't supported, an error is much more welcome than a hard-to-debug hang.
function!s:SetGUIOptions()
" If we're in a Neovim GUI, such as Neovim-GTK…ifhas("nvim")
Guifont SourceCodePro:h12
endifendfunctionifhas("gui_running")
call<SID>SetGUIOptions()
endif
Technical information (please complete the following information):
Describe the bug
When running neovim-gtk with 0.9.4 or nightly installed, with the below
.vimrc
(tested usingnvim-gtk -- -u FILE
), Neovim fails to initialize with the error messages below. Note that this problem does not occur with 0.7.2. I don't believe the font is relevant; usingmonospace:h12
triggers the problem just as well.I believe the problem is related to the fact that the newer versions set
gui_running
. I use a.vimrc
that's shared between Vim and Neovim, so I used to have a branch for gvim (has("gui_running")
) which simply called mySetGUIOptions
function, and a branch for Neovim which did that onUIEnter
.Obviously I can change the order, but it seems less than ideal for neovim-gtk to hang when
Guifont
is invoked during startup. I should note that Neovim-Qt with 0.9.4 simply complains about the lack ofGuifont
, so it doesn't appear that this is an intrinsic limitation of newer versions of Neovim. If this isn't supported, an error is much more welcome than a hard-to-debug hang.Error messages below:
.vimrc
:Technical information (please complete the following information):
50f27f5a06582a7fb6b9fa03ca5f2d21d466c181
(currentHEAD
)The text was updated successfully, but these errors were encountered: