You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
I was cleaning up and adding some plugins around the time of the latest commit. I have paq configured to manage itself, so a :PaqSync probably updated it. I get this when running PaqSync now:
E5108: Error executing lua ...cal/share/nvim/site/pack/paqs/start/paq-nvim/lua/paq.lua:98: Cannot serialise function: type not supported
stack traceback:
[C]: in function 'error'
...cal/share/nvim/site/pack/paqs/start/paq-nvim/lua/paq.lua:98: in function 'state_write'
...cal/share/nvim/site/pack/paqs/start/paq-nvim/lua/paq.lua:297: in function 'exe_op'
...cal/share/nvim/site/pack/paqs/start/paq-nvim/lua/paq.lua:353: in function 'clean'
...cal/share/nvim/site/pack/paqs/start/paq-nvim/lua/paq.lua:354: in function 'sync'
[string ":lua"]:1: in main chunk
I removed the last plugin I added before the error, thinking it might be the cause, but the error remained. After some commenting, I've narrowed it down to this line in my config:
I've added a very primitive lockfile mechanism (#147) and was merge like 2 hours ago. The main issue is that vim.json.encode doesn't support decoding functions into json.
As a quickfix I will suggest you to pass to the run function directly the vim command you want to execute, like so:
Describe the bug
I was cleaning up and adding some plugins around the time of the latest commit. I have paq configured to manage itself, so a
:PaqSync
probably updated it. I get this when running PaqSync now:I removed the last plugin I added before the error, thinking it might be the cause, but the error remained. After some commenting, I've narrowed it down to this line in my config:
There's no errors if I simply have
"nvim-treesitter/nvim-treesitter",
instead.To Reproduce
Use the following with
nvim -u
:Expected behavior
No errors.
Environment:
nvim --version
:The text was updated successfully, but these errors were encountered: