Issue with using nvim +terminal

[Trid-collab]

Hi, I am new to startify. After configuring to be used with my nvim. I find that when I try " nivm +terminal" it opens my nvim startify page instead of my nvim term. I found that if I disable startify "nvim +terminal" works fine. Could help directing me to where the issue is

let g:startify_padding_left= 10 let g:startify_session_peristence =1 let g:startify_enable_special=0 let g:startify_change_to_vcs_root= 1 let g:startify_lists [..]

[mhinz]

Hmm, that's a bit strange. This plugin checks on :h VimEnter if the first buffer is empty or not.

Please put autocmd VimEnter * echomsg 'FOO: '. line2byte('$') in the init.vim and restart nvim +term. Check :messages in case you don't see the message. I assume you're getting -1 although you shouldn't.

BTW, if you're using an alias/shell function for starting nvim +term, you could use nvim +'let startify_disable_at_vimenter = 1 | terminal' instead.

Which Nvim version are you using?

[Trid-collab]

I am using the nvim 0.4.4 on Ubuntu 20.04 on WSL2 . There is no improvement in the issue. I have tried using nvim +'let startify_disable_at_vimenter = 1 | terminal' as suggested . Even then it opens the Startify page

[mhinz]

But what's the output of the autocmd I mentioned above?

On another note, although 0.4.4 is the current release, it's pretty old already. Maybe it's fixed on master already, so try using a nightly:

See https://github.com/neovim/neovim/releases/tag/nightly, e.g. https://github.com/neovim/neovim/releases/download/nightly/nvim-win64.zip.

[shaggyrogers]

I failed to reproduce this on nvim 0.5.1, so it may have been fixed or it could occur as a result of your particular setup. In the latter case, a solution might involve checking &buftype in s:on_vimenter().