Closed nyngwang closed 1 year ago
Can't reproduce. I tried opening two buffers, splitting them in two, and saving session :mksession some.vim
. Then I opened nvim via nvim -S some.vim
and I get no errors.
Could you add more details.
Could you add more details.
@utilyre In my DEMO I restore the session where I created more than 1 tabpage. Might be related... If still cannot reproduce then I have no idea, since the error message seems to point out that the culprit is related to a window-plugin. The tabpage management tool I'm using is Tabby but I guess this is not related.
Please provide a minimal config according to lazy.nvim's Wiki.
@utilyre Hi, it turns out this is a wrong report. Apologies. The problem is still happening after some standalone testing with windows.nvim without barbecue.nvim. Closing...
Description
As title. I got the error message:
If I disable barbecue.nvim then the error is gone. (I reported this in anuvyklack/windows.nvim too, but it looks like the author has abandoned the issues section since there are some issues created in Sep. without any reply.)
Reproduce
To reproduce, you can use my config (assuming you use packer.nvim):
https://user-images.githubusercontent.com/24765272/209852868-a8e2d7e1-c960-4a11-9cc2-f0c75a448d5f.mov