Closed jdhao closed 2 years ago
Upon inspecting the neovim help on startup
, it seems that VimEnter
event is fired after +cmd
, so alpha-nvim is overriding the buffer created by Man!
command. It seems that alpah-nvim should add a check condition for the existing buffer?
hmm the hotfix is just to change +Man!
to -c Man!
, i have not been able to find a set of predicates for alpha opening that doesn't break any plugins https://github.com/goolord/alpha-nvim/blob/main/lua/alpha.lua#L396
@goolord Would like me to make a pull request for this?
to 2., yeah i think that would be the optimal solution but i think this would probably break the plugin if someone aliases neovim or something. i'm unsure. i'll look at the neovim manpage some time and see if that's an option, atm the behavior is supposed to be closer to how startify/dashboard check
@goolord you mean the user does something like this in their shell startup file: alias nvim="nvim -someoption"
?
I am not aware of the usefulness of this alias after inspecting the nvim command line options.
Maybe we can just disable alpha-nvim once a command line argument is detected. If a user later complains about this, then collect their use cases and adjust the skip strategy.
Anyway, IMHO, the skip condition should be made a separate function to make the code cleaner.
should be fixed by https://github.com/goolord/alpha-nvim/pull/47
I am using neovim as my man pager using the following shell config:
without alpha nvim, it works well when I run
man ls
. After using alpha-nvim, nvim opens, but the alpha-nvim start page is shown instead of the man page.