четверг, 25 октября 2012 г., 8:41:03 UTC+4 пользователь MarcWeber написал:
Sorry, if you don't have a terminal you don't use gvim --help usually.
Anybody who did proof me wrong, please.
Thus it should be fine to print --help output before starting the gui
and everything should be fine.
My
The idea is that when there is no terminal, gvim is started from the
desktop, the output of --help is displayed in a GUI window. Thus you
can't set gui.starting to FALSE in general.
Where does it disappear on my system then? Both --help and --version show
nothing when compiling latest
I'm in a situation where saving the values of window-local variables would be
useful. It seems that sessionoptions does not have an option for
window/buffer local variables saving.
It would be nice to generalize the 'globals' so that a local window/buffer
variable like b:Saveme would be
On 25-Oct-2012 09:29:08 +0200, Ron Aaron wrote:
I'm in a situation where saving the values of window-local variables
would be useful. It seems that sessionoptions does not have an
option for window/buffer local variables saving.
It would be nice to generalize the 'globals' so that a local
On 25/10/12 3:17 PM, Bram Moolenaar wrote:
Ben Schmidt wrote:
I think E163 could do with some rewording, or perhaps another error
could be created. It seems E163 is used when there are less than two
arguments, and E165 or E164 when there are two or more. However, the
case when there are zero
Eg do this and be done: system(s:async.vim.' --help') !~ '--servername'
Why not stridx(system(s:async.vim.' --version'), '+clientserver')!=-1?
--help was the first thing I tried which worked. using --version is
better of course - but who cares?
My code only does the check if vim is used - and
FWIW, on Unix if you manage to get such a variable into the environment (bash
won't let you)
:echo libcall('', 'getenv', '$ProgramFiles(x86)')
will show it to you.
Surely, there's a better way.
Regards, John
--
You received this message from the vim_dev maillist.
Do not top-post! Type your
