diff options
| author | tao <2471314@gmail.com> | 2026-06-11 05:28:17 +0800 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2026-06-10 17:28:17 -0400 |
| commit | b49492f13ce34c242546e5a3e768b2937ebddeba (patch) | |
| tree | 9aab9a4bc4ca613f9acc466a87357f6cf598945b /runtime/lua/vim/provider/python.lua | |
| parent | 2899e350ff06833af0d53baba31800a32dcea696 (diff) | |
| download | rneovim-b49492f13ce34c242546e5a3e768b2937ebddeba.tar.gz rneovim-b49492f13ce34c242546e5a3e768b2937ebddeba.tar.bz2 rneovim-b49492f13ce34c242546e5a3e768b2937ebddeba.zip | |
fix(option): set 'shell…' options based on detected shell #40031
Problem:
* 'shellcmdflag' states that its default value is set according to the
value of 'shell', but this behavior is not yet implemented on Windows.
The same applies to 'shellpipe', 'shellredir', and 'shellxquote'.
* On Windows, Git is often installed in paths containing spaces, and we
still do not correctly resolve the sh executable name as described in
'shell'.
* On Windows, the default value of 'shellslash' is always `false`,
which causes Unix-like shells to interpret `\` in paths returned by
some functions as escape charaters.
Solution:
Use a simple rule table to detect common shells (e.g. `cmd`,
`powershell`, shells whose names contain `csh` or `sh`) and apply
best-effort defaults, while leaving more complex scenarios to user
configuration.
Diffstat (limited to 'runtime/lua/vim/provider/python.lua')
0 files changed, 0 insertions, 0 deletions