What is the user case for --remote-silent without a file name?
Start editing an empty buffer?
A simple solution might be the one attached below. Don't know however,
if there are any side effects. Works for me.
It has side effects. You probably want to use :enew or :new instead
of :drop.
@Bram
I often just open GVim (Windows 7, 64 bit) w/o any file name. As I always use
the OLE version of GVim, and only want/need one incarnation of GVim - so I have
to start GVim with '--remote-silent ', resulting in the above mentioned error
message; omitting the '' ('--remote-silent')
A simple solution might be the one attached below. Don't know however, if there
are any side effects. Works for me.
--- x\main.c2013-12-30 13:27:49.756908800 +0100
+++ main.c 2013-12-30 13:22:35.739224000 +0100
@@ -3892,13 +3892,13 @@
}
/*
- * Build a :edit command to send to a Vim
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
On Thu, Sep 26, 2013 at 12:04 PM, Axel Bender
axel.ben...@cip-kommunal.de 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
Any official reply to this?
--
--
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
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
