bug: In Windows, there is a conflict between `plenary` and `vim.opt.shellslash = true`.
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- lua, vim
- Domain
- operating-systems, tooling
Research direction
Reproduce the issue on Windows with plenary and vim.opt.shellslash = true, using the attached example as the starting point. Trace where plenary handles path separators and compare behavior with and without shellslash; done means plenary operates normally without the reported conflict.
Written by the indexing model from the issue text.
Description
It's not that the '/' symbol for path separation won't appear in Windows.
If the '/' separator appears in Windows, it will cause abnormal operation. I made the following modifications to make it work properly for now.
- Dominant language
- Lua
- Stars
- 3.5k
- Forks
- 340
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from nvim-lua/plenary.nvim
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
nvim-lua/plenary.nvim#682 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
nvim-lua/plenary.nvim#680 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
nvim-lua/plenary.nvim#675 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 28/100
nvim-lua/plenary.nvim#672 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
nvim-lua/plenary.nvim#671 · 1 comment ·
All issues in nvim-lua/plenary.nvim
Similar issues
-
Zenmap
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 5 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
revisit-at-release statusline
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
neovim/neovim#42188 · 1 comment ·
Maintainers usually reply within 1 day
-
[Aska] IssueOpen
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
pterodactyl/game-eggs#640 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 2 days