On 26/09/13 18:04, Axel Bender wrote:
At the moment, when starting "gvim --remote-silent" gvim would display an error
message, indicating that no file name was provided.
This is quite a nasty behavior if you - like me - at times just start gvim (using a macro including
"--remote-silent") w/o a file name just to get gvim "up and running" as an OLE
server in the background.
I don't think that the necessity to provide a file name is a real requirement, but just a
relic from the beginnings of the implementation for "--remote-silent".
The same holds for "--remote" and "--remote-tab".
This is no "official response" (only Bram can give that) but I suppose
you could run "gvim --serverlist" first (or "vim --serverlist" if your
Console Vim was built with +clientserver) and then start "gvim
--servername {name}" in the background (using start on Windows or a
command-line ending in & on Unix bash) only if it isn't already running
with the desired servername (or omit the --servername {name} part, but
not if running as root (superuser) IIUC, to get the default name).
Best regards,
Tony.
--
hundred-and-one symptoms of being an internet addict:
36. You miss more than five meals a week downloading the latest games from
Apogee.
--
--
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.
