mhinz / vim-startify

:link: The fancy start screen for Vim.
MIT License
5.31k stars 186 forks source link

Startify not starting up Neovim? #420

Open djasnowski opened 4 years ago

djasnowski commented 4 years ago

On nvim 0.4.3 (macOS Catalina), I just added this line to my neovim config https://gist.github.com/naknode/f8f9aab6b758d05df900afe340713219 Plug 'mhinz/vim-startify' and I still do not see this on startup.

I added the same line to my even more simpler vim config and alas, no startup. On either. What am I doing wrong? Is this not a startup screen?

And yes :Startify does indeed work.

little-fish-lalala commented 4 years ago

On nvim 0.4.3 (macOS Catalina), I just added this line to my neovim config https://gist.github.com/naknode/f8f9aab6b758d05df900afe340713219 Plug 'mhinz/vim-startify' and I still do not see this on startup.

I added the same line to my even more simpler vim config and alas, no startup. On either. What am I doing wrong? Is this not a startup screen?

And yes :Startify does indeed work.

I have the same question.

little-fish-lalala commented 4 years ago

https://github.com/mhinz/vim-startify/issues/420#issuecomment-624073856
I solved the problem by setting this in my .zshrc: alias vim="nvim +:Startify"

ghost commented 4 years ago

In my case, I could solve if by adding autocmd VimEnter * Startify to my .vimrc.

mhinz commented 4 years ago

Sorry for not being active the last months.

Is this still an issue? This really shouldn't happen at all.

On the VimEnter event, this code is run: https://github.com/mhinz/vim-startify/blob/04ad724e80f51a3f119c0453966c336ce052752c/plugin/startify.vim#L37-L41

So, by default it should act the same as autocmd VimEnter * Startify, if vim is called without any arguments, starts with an empty buffer (so if another plugin is run before Startify, it could fill the buffer) and g:startify_session_autoload isn't set to 1, it should run automatically.

You could drop an echomsg "FOO" between lines 37 and 38 above, to see if that code is even run at startup.

stephane-klein commented 2 years ago

Is this still an issue? This really shouldn't happen at all.

@mhinz no issue with NeoVim 0.5.1, I think you can close the issue 👍