Closed peacock0803sz closed 4 months ago
Hm... It works for me.
There was no problem with deno v1.43.1 or Linux, so it might deno problem....?
I might have faced the same issues on my mac os.
It was resolved using the deno by the official installer. https://deno.com/ I'm not sure the reason why.
I used the deno installed by Homebrew. Then, the cause may be Homebrew.
I have not faced this issue and also have not reproduced it with minimal init.vim
I'm using:
Oh, It does not occur with official binary from denoland, Probably that's homebrew issue π
Exactly. I found the cause issue at denoland/deno π― https://github.com/denoland/deno/issues/23766
It's not denops's problem, I'll close this issue π Thank you to @mopp @ryota2357 for checking/sharing conditions :)
Description
Deno start denops process (only for macOS?) since deno@1.43.2, but It can do correctly with deno@1.43.1 (previous version).
Environment Info
14.4.1
(arm64)1.43.2
NVIM v0.10.0-dev-3103+gca735c755
)v0.9.5
)Expected behavior
Works with deno v1.43.2 (latest) in macOS
Step to reproduce
Starting denops shared server with
deno run -A --no-lock path/to/vim-denops/denops.vim/denops/@denops-private/cli.ts --hostname=127.0.0.1 --port=32123
, and createinit.vim
as following.Then, start Neovim with the
init.vim
(nvim -U NONE -u init.vim
), the deno process will crash with segmentation fault like bellowThe log message in Neovim (with
:messages
) as is: