>> 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... >> >> > > The intent of the implementation was to make this work by default: > > :!"C:\Program Files\something\app.exe" "C:\Documents and > Settings\user1\blah.txt" > > The old defaults would make this fail by stripping off the first and last > parenthesis. The current defaults were the best we could come up with in a > series of patches: 7.3.443, 7.3.445-7.3.448, and 7.3.450. > > Your problem looks very similar to this: > > https://groups.google.com/d/topic/vim_dev/Uxx5KcB7ktA/discussion > > But in that case, escaping with ^ seemed to work. > > I do think your use case was why the "( support was added. > > I think I remember that "echo" is special and doesn't work the same as > calling an actual application, as well. > > By the way, changing the command to: > > :!cmd /c "echo b(l)ah" > > also works, with default option values. This works around the special-ness of > "echo" if that's actually the case.
So how would you run a valid cmd.exe line "c:\program files (x86)\xyz\xyz.exe" "arg1 with spaces" "arg 2 with spaces" from a script rather than exe 'r!cmd.exe /c ""c:\program files (x86)\xyz\xyz.exe" "arg1 with spaces" "arg 2 with spaces""' which does not work with default settings under 7.4 (I patched it today using short file names, but that is no solution)? And what to do to run this for 7.3 (some version before the patch) AND 7.4? 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.
