ThePrimeagen / ThePrimeagen/init.lua
Errors with vim.cmd and vim.lsp.buf.format
Open
Nobody has claimed this yet.
- Dominant language
- Lua
- Stars
- 4k
- Forks
- 680
- PR merge metrics
- No merged PRs in 30d
Description
I was going through and updating my config files and Neovim complained about the following:
- In packer.lua :
vim.cmd.packeradd("packer.nvim")- Resolved by changing to
vim.cmd [[packeradd packer.nvim]]
- Resolved by changing to
- In packer.lua :
vim.cmd.colorscheme("tokyonight")- Resolved by changing to
vim.cmd [[colorscheme tokyonight]]
- Resolved by changing to
- In remap.lua :
vim.cmd.Ex- Resolved by changing to
":Ex<CR>"
- Resolved by changing to
- In remap.lua :
vim.lsp.buf.format- Resolved by changing to `function() vim.lsp.buf.format {} end)
I'm not sure what changed, but it affected 1 of 2 of my linux installs as well as my windows install.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the reported errors in packer.lua and remap.lua on the affected Linux and Windows installations, then compare the relevant Neovim or Vim versions. Trace the behavior of vim.cmd, vim.cmd.Ex, and vim.lsp.buf.format; done means identifying the version or configuration difference and documenting a confirmed compatible invocation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- lua, vim
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100