E182: Invalid command name in plenary.nvim/plugin/plenary.vim in WSL2

Open
#467 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
lua
Domain
devtools

Research direction

Start with plugin/plenary.vim, especially lines 2 and 4, and reproduce the E182 errors in the reported WSL2 setup. The work is done when the plugin loads without those invalid-command errors and the affected commands remain usable.

Written by the indexing model from the issue text.

Description

" Create command for running busted
command! -nargs=1 -complete=file PlenaryBustedFile lua require('plenary.busted').run(vim.fn.expand(""))
command! -nargs=+ -complete=file PlenaryBustedDirectory lua quire('plenary.test_harness').test_directory_command(vim.fn.expand(""))
nnoremap PlenaryTestFile :lua require('plenary.test_harness').test_directory(vim.fn.expand("%:p"))

Error detected while processing /home/poorjack/.local/share/nvim/site/pack/packer/start/plenary.nvim/plugin/plenary.vim:
line 2:
E182: Invalid command name
line 4:
E182: Invalid command name

Dominant language
Lua
Stars
3.5k
Forks
340
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

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.

More from nvim-lua/plenary.nvim

All issues in nvim-lua/plenary.nvim

Similar issues

More Lua issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.