On Friday, November 3, 2017 at 1:49:18 PM UTC-6, Ben Fritz wrote: > > "-c", > > "\"%s/.*foo.*/bar/g | w\"",
> Why gvim and not console vim? I don't know if it is the cause, but if you > must use gvim then on Linux and similar systems you need to also pass the > "-f" argument if you want your code to wait for gvim to be exited. This > doesn't work in Windows, but the official installer can create a .bat file > with an implementation of a similar feature. Hi Ben, What solved it was multiple invocations of -c, one for each command. I don't have a preference on gvim versus vim, however the next time I am making changes I will explorer that just for curiosities sake. Thanks. -- -- You received this message from the "vim_use" 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_use" 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/d/optout.
