Viktor Kojouharov wrote:
Hi Bram,
I made a patch which adds a new variable, 'v:progpath'. Quite similar
to 'v:progname', but including the full invocation path of the current
vim instance. The full path itself is quite useful when you want to do
tricks with vim servers and --remote-expr,
Hi Bram,
I made a patch which adds a new variable, 'v:progpath'. Quite similar to
'v:progname', but including the full invocation path of the current vim
instance. The full path itself is quite useful when you want to do tricks with
vim servers and --remote-expr, and you don't have to care
It contains the full path which was used to start vim. It could very well be a
relative path, or be the same as progname, if vim was run started from the
$PATH, but wouldn't the value be enough to start another instance of vim?
On Thursday, March 13, 2014 11:25:35 PM UTC+2, Gary Johnson wrote:
On 2014-03-13, Viktor Kojouharov wrote:
On Thursday, March 13, 2014 11:25:35 PM UTC+2, Gary Johnson wrote:
On 2014-03-13, Viktor Kojouharov wrote:
Hi Bram,
I made a patch which adds a new variable, 'v:progpath'. Quite
similar to 'v:progname', but including the full invocation path
On Friday, March 14, 2014 2:04:26 AM UTC+4, Viktor Kojouharov wrote:
It contains the full path which was used to start vim. It could very well be
a relative path, or be the same as progname, if vim was run started from the
$PATH, but wouldn't the value be enough to start another instance of
