> :r! cmd /c echo B(la)h
>
> is broken. It is neither executed nor a piped outline file is
created, so VIm can't read the output and throws a read error on temp
file. This is working under 7.3 without problems.
>
> Anyone an idea where to start bug hunting?
>
:verbose set shellcmdflag? shellxquote? shellxescape? shell?
Halfway through Vim 7.3 patches, the 'shellxescape' option was added
and defaults for the others modified so that Windows shell commands
succeeded more often. But they still fail with some special
characters, because cmd.exe quoting is "special".
For once I'm posting from a Linux system and can't test at the
moment. Try with these options at their default value. If these
options are still at their defaults, I think you can try shellxquote
as "(
shellcmdflag=/c
shellxquote=(
shellxescape="&|<>()@^
shell=C:Windowssystem32cmd.exe For Win32 the default for
shellxquote is ( so the shellxescape characters will be escaped by ^.
The help file and implementation is correct, but cmd.exe does not
understand the escaped ^(
:!echo b(l)ah
C:Windowssystem32cmd.exe /c (echo b^(l^)ah)
"ah)" kann syntaktisch an dieser Stelle nicht verarbeitet werden.
shell returned 1
Hit any key to close this window...
Using "( works, no escape characters will be used. But I do not
understand
a) the goal of this implementation
b) the non working default setting for Win32
Of course I do not want to run an "echo" but "c:program Files
(x86)...." and this behaviour will break many plugins...
Best regards,
Jan
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
