Closed sonique6784 closed 5 months ago
Hi @sonique6784,
Thank you for reporting this issue.
The VimEnter
event triggers the initialization of some global variables in the tabby#OnVimEnter
function. So if it is not triggered, commands may result in script errors.
Currently, there is no log output available for debugging the vim-tabby
script. It would be helpful to know if you have added any options to enable lazy loading of vim-tabby
. This could load the script after the VimEnter
event has already passed, causing issues.
I think I should improve the initialization flow to support proper lazy loading in the future 🤔
Hi @icycodes, thanks for your reply. please find below my nvim configuration for Tabby: After reading your message I tweaked the configuration as below and it works fine now.
-- /.config/nvim/lua/plugins/tabby.lua
return {
"TabbyML/vim-tabby",
cmd = "Tabby",
lazy = false, -- < This fixed the issue and load Tabby properly
}
issue is fixed, make sure to add
lazy = false
so the plugin is not lazy loaded
Issue
I'm using nvim with AstroVim and Lazy.
It seems that tabby is half-loaded
in
Lazy
tabby is loaded:When I try to know tabby' status, I get "initializing", but it doesn't go any further.
Temporary solution
if I run
:doau VimEnter
then tabby initialise. so I believe theVimEnter
event is not trigger by default with nvim.Other info
When I try other commands like version or help, I get some errors:
is there a log somewhere to know why the plugin is stuck?