VSCodeVim / VSCodeVim/Vim

Configuration: Invalid neovimPath. Using neovim installed via snap

Open
#4,931 4 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
15.2k
Forks
1.5k
Avg merge
3d 18h
Merged PRs (30d)
6

Description

Describe the bug

I've neovim installed via Snap(https://github.com/neovim/neovim/wiki/Installing-Neovim#snap):

➜ /snap/bin/nvim --version
NVIM v0.5.0-nightly-6-gef0398f
Build type: Release
LuaJIT 2.1.0-beta3
Compilation: /usr/bin/cc -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -O2 -DNDEBUG -Wall -Wextra -pedantic -Wno-unused-parameter -Wstrict-prototypes -std=gnu99 -Wshadow -Wconversion -Wmissing-prototypes -Wimplicit-fallthrough -Wvla -fstack-protector-strong -fno-common -fdiagnostics-color=always -DINCLUDE_GENERATED_DECLARATIONS -D_GNU_SOURCE -DNVIM_MSGPACK_HAS_FLOAT32 -DNVIM_UNIBI_HAS_VAR_FROM -DMIN_LOG_LEVEL=3 -I/root/parts/nvim/build/build/config -I/root/parts/nvim/build/src -I/root/parts/nvim/build/.deps/usr/include -I/usr/include -I/root/parts/nvim/build/build/src/nvim/auto -I/root/parts/nvim/build/build/include
Compiled by root@snapcraft-nvim

Features: +acl +iconv +tui
See ":help feature-compile"

   system vimrc file: "$VIM/sysinit.vim"
  fall-back for $VIM: "/usr/share/nvim"

Run :checkhealth for more info

After setting:

"vim.neovimPath": "/snap/bin/nvim", it gives me the error:

Configuration: Invalid neovimPath. Command failed: /snap/bin/nvim --version need to run as root or suid .

But as you could see above, there is no root needed to run /snap/bin/nvim --version.
Also I can reproduce #4902 where I get:

Configuration: Invalid neovimPath. The argument 'file' cannot be empty. Received ''.

To Reproduce

Install nvim via snap:

  1. sudo snap install --beta nvim --classic
  2. Set "vim.neovimPath": "/snap/bin/nvim", in thesettings.json with neovim enabled

Expected behavior

No error message.

Environment (please complete the following information):

  • Extension (VsCodeVim) version: 1.14.5
  • VSCode version: 1.45.1
  • OS: Ubuntu 18.04.4 LTS

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing validation of the vim.neovimPath setting and the command execution used for /snap/bin/nvim, then reproduce the issue with the snap installation and settings.json configuration described. Done means the extension accepts this path and reports no invalid-configuration error while retaining the existing behavior for other Neovim paths.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
tooling
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.