Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bug: cannot use vscode extra plugin #798

Closed
3 tasks done
fveauvy opened this issue May 22, 2023 · 0 comments · Fixed by #796
Closed
3 tasks done

bug: cannot use vscode extra plugin #798

fveauvy opened this issue May 22, 2023 · 0 comments · Fixed by #796
Labels
bug Something isn't working

Comments

@fveauvy
Copy link

fveauvy commented May 22, 2023

Did you check docs and existing issues?

  • I have read all the LazyVim docs
  • I have searched the existing issues of LazyVim
  • I have searched the existing issues of plugins related to this issue

Neovim version (nvim -v)

NVIM v0.9.0

Operating system/version

MacOS 13.3.1

Describe the bug

After starting vscode, I have this error in the output of vscode-neovim :


Error detected while processing /Users/fveauvy/.config/nvim/init.lua:
E5113: Error while calling lua chunk: .../nvim/lazy/LazyVim/lua/lazyvim/plugins/extras/vscode.lua:28: attempt to call field 'list_contains' (a nil value)
stack traceback:
	.../nvim/lazy/LazyVim/lua/lazyvim/plugins/extras/vscode.lua:28: in function 'update_state'
	...local/share/nvim/lazy/lazy.nvim/lua/lazy/core/plugin.lua:418: in function 'load'
	...local/share/nvim/lazy/lazy.nvim/lua/lazy/core/loader.lua:36: in function 'setup'
	...eauvy/.local/share/nvim/lazy/lazy.nvim/lua/lazy/init.lua:75: in function 'setup'
	/Users/fveauvy/.config/nvim/lua/config/lazy.lua:9: in main chunk
	[C]: in function 'require'
	/Users/fveauvy/.config/nvim/init.lua:2: in main chunk

I was curious and enabled the vscode extra plugin from LazyVim.
I followed the installation steps of the vscode extension "VSCode Neovim".

Steps To Reproduce

  1. Add the vscode extra plugin in the lazy.lua file.
  2. Restart Neovim.
  3. Install VSCode Neovim extension in vscode
  4. Add "extensions.experimental.affinity": { "asvetliakov.vscode-neovim": 1 }, to my vscode settings.
  5. Restart vscode.

I tried to disable all the other extensions in vscode, but to no avail.

Expected Behavior

The vscode extension should process init.lua on startup.

Repro

-- DO NOT change the paths and don't remove the colorscheme
local root = vim.fn.fnamemodify("./.repro", ":p")

-- set stdpaths to use .repro
for _, name in ipairs({ "config", "data", "state", "cache" }) do
  vim.env[("XDG_%s_HOME"):format(name:upper())] = root .. "/" .. name
end

-- bootstrap lazy
local lazypath = root .. "/plugins/lazy.nvim"
if not vim.loop.fs_stat(lazypath) then
  vim.fn.system({ "git", "clone", "--filter=blob:none", "https://github.com/folke/lazy.nvim.git", lazypath, })
end
vim.opt.runtimepath:prepend(lazypath)

-- install plugins
local plugins = {
  "folke/tokyonight.nvim",
  "folke/LazyVim",
  -- add any other plugins here
}
require("lazy").setup(plugins, {
  root = root .. "/plugins",
})

vim.cmd.colorscheme("tokyonight")
-- add anything else here
@fveauvy fveauvy added the bug Something isn't working label May 22, 2023
@folke folke closed this as completed in 3dcc074 May 23, 2023
ofrades pushed a commit to ofrades/LazyVim that referenced this issue May 30, 2023
joshmedeski pushed a commit to joshmedeski/LazyVim that referenced this issue Sep 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant