win32 does not necessarily mean cmd.exe as well as others does not mean sh.
Problem is, that previous functions, like s:escape_cword() do respect shell e.g.
with shellescape(), but passing the arguments to job_start() / jobstart()
does ignore shell.
This leads to trouble. E.g. I use fish, where shellescape() escapes \, which means
if <cword> / -cword is used (e.g. Aword), s:escape_cword() results to \\bAword\\b
(which is correct), but this string is then passed to jobstart() executed by
sh, which does not share the same escaping rules.
win32 does not necessarily mean
cmd.exeas well as others does not meansh.Problem is, that previous functions, like s:escape_cword() do respect
shelle.g. withshellescape(), but passing the arguments tojob_start()/jobstart()does ignoreshell.This leads to trouble. E.g. I use
fish, whereshellescape()escapes\, which means if<cword>/-cwordis used (e.g.Aword),s:escape_cword()results to\\bAword\\b(which is correct), but this string is then passed tojobstart()executed bysh, which does not share the same escaping rules.