-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fail to start up #106
Comments
Hey! Thanks for the issue report. I don't know if anyone has yet tried to install this plugin with
The next step would be to try to enable logging and see if there's anything useful in the logs. On Linux, the logs are by default at |
Thanks very much for your quick reply and sorry for my delayed answer. I'm leaving vim-plug papis.nvim installation until I understand plugin managers concepts a bit more. Sorry for messing up the issue report. Now I made a fresh LazyVim installation with papis.nvim (and dependencies) only, deleted former ~/.local/share/nvim, reset this folder and got the following results:
Papis is installed, of course. It has been used for years. |
Can you enable the debug module and check the logs? I've also just pushed a change that should avoid the |
This is yet another start up case, pretty much like #104. My checkhealth results are the same the user showed, but I don't understand what he did to get a better response of the plugin installation.
So...
:Papis reload data
at start up.I installed papis.nvim with vim-plug and LazyVim in two different configurations, and reinstalled it in both several times, too, getting the same problems indistincly. However, if vim-plug is supported, I actually prefer to fight on that one since I know this configuration very well.
My set up in Lazy is this:
And, in the other configuration, my plugins part of the init.vim is this:
Thanks very much in advance.
The text was updated successfully, but these errors were encountered: