bug: In Windows, there is a conflict between `plenary` and `vim.opt.shellslash = true`.

Open
#646 0 comments 0 reactions 0 assignees View on GitHub

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.

Image

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.