On 17-Feb-2012 13:34, Andy Wokula wrote: > Am 15.02.2012 19:36, schrieb Andy Wokula: >> Am 15.02.2012 17:22, schrieb Ben Fritz: >>>> New settings: >>>> shellcmdflag: /c >>>> shellxquote: ( >>>> and escape special chars with `^'. >>> >>> So you're saying, we must escape all special characters, INCLUDING >>> QUOTES, and surround in parentheses? >> >> Yes, including quotes! >> >>> That's...special. >> >> But solves all problems so far. > > Please, somebody with a Windows 7 / Vista / Win 2003 machine: > > Does the following edit new&file.txt ? > > cmd /c (notepad ^"new^&file.txt^") > > It works here on good ol XP. > > I suspect that shell quoting has changed since: > Is it ok to escape the double quotes? > > And, similar, > Does the following output the contents of new&file.txt ? > cmd /c (type ^"new^&file.txt^") > > or does it output something like > Error, not a command: "file.txt")" > > The error case would be awful.
Works on both Vista Professional 32-bit and 7 Ultimate 64-bit, both in a command prompt and from the Start > Run... dialog. I feel your pain; cmd.exe [quoting] is awful. Thanks for putting so much energy into it! -- regards, ingo -- 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
