Open romgrk opened 2 years ago
Forget all of the above. The root cause is a namespace conflict with https://github.com/notomo/promise.nvim.
Both that plugin and your promise-async
try to use the require('promise')
namespace in lua.
Even though I have no idea to fix it, please show path about promise-async
and promise.nvim
.
Both installed with vim-plug. If you see on that repo, they use ./lua/promise.lua
as well. You'll need to decide by a duel who keeps the name. Ping @notomo.
The best solution is probably to upstream either one of these into neovim.
I think ufo can add post-installation to install promise-async
inside the plugin, depending on the user who has a promise
and async
module outside ufo.
@romgrk
Hi. I don't expect notomo/promise.nvim
to be installed directly.
You can use my promise.nvim by embedding in your plugins namespace.
ref: https://github.com/notomo/promise.nvim/blob/10b86664130f9668f0fa6549bda660794417aaf7/README.md#L4-L4
Mainly used by embedding
lua/promise/init.lua
in plugins.
Neovim version (nvim -v | head -n1)
0.8.0-dev
Operating system/version
archlinux
How to reproduce the issue
Expected behavior
Plugin works
Actual behavior
There are a few issues, first one is:
It is solved by add
require('promise').new(...)
here: https://github.com/kevinhwang91/nvim-ufo/blob/cf7dc7fa196dbb835a1b8bbc5d7c5f6d786f41ee/lua/ufo/utils.lua#L104The second issue (after fixing the one above) is: