On Wednesday, September 11, 2013 6:43:02 AM UTC-5, jan.s...@t-online.de wrote:
> Hi,
>
>
>
> if you read with
>
>
>
> - Vim 7.4.22 (32bit)
>
> - Windows 7 (x64)
>
>
>
> from a command line output by
>
>
>
> :[range]r[ead] [++opt] !{cmd}
>
>
>
> and using parenthesis the command is completly broken.
>
>
>
> If you write
>
>
>
> :r! cmd /c echo Blah
>
>
>
> you get "Blah"
>
>
>
> :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 "(
Yes, that's two characters, including a " character.
--
--
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 vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
