On Wed, September 11, 2013 15:35, Jan Stocker wrote: >> :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? > > > > I think, you need to escape the parenthesis with '^'. > > No this does not work either, if shellxquote is ( vim does this > automatically, you can proof this by > > :!echo b(l)ah > > Sorry, only a German system available. > > 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...
Hm, interesting. I confirm, I don't understand the quoting rules completly and there were always cases, when it didn't work on Windows. Interestingly, there are some differences between calling :r !echo and :!echo :!echo bl(ah) cmd.exe /c (echo bl^(ah^)) ")" kann syntaktisch an dieser Stelle nicht verarbeitet werden. shell returned 1 Hit any key to close this window... :!echo "bl(ah)" cmd.exe /c (echo ^"bl^(ah^)^") "bl(ah)" Hit any key to close this window... :r !echo bl(ah) Rufe Shell auf, um "echo bl(ah) > C:\Users\DE914854\AppData\Local\Temp\VIoB10D.tmp" auszuführen E485: Kann Datei C:\Users\DE914854\AppData\Local\Temp\VIoB10D.tmp nicht lesen no output :r !echo bl^(ah^) Rufe Shell auf, um "echo bl^(ah^) > C:\Users\DE914854\AppData\Local\Temp\VIo1839.tmp" auszuführen output: bl(ah) :r !echo "bl(ah)" Rufe Shell auf, um "echo "bl(ah)" > C:\Users\DE914854\AppData\Local\Temp\VIoD0E0.tmp" auszuführen output: "bl(ah)" regards, Christian -- -- 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.
