Whether Bram thinks it's useful to store this info in some
v:variable (so script can know it) ?
Within last year, there were requests how script can know
whether vim had +NUM option on command line.
Yakov
A.J.Mechelynck [mailto:[EMAIL PROTECTED] wrote:
> I don't know where that 4-part version number comes from. 262 can be
> interpreted as 262d, 106h, 406o, ^F^A (the latter assumes one little-endian
> word),... none of which rings any bells with me.
It comes from version.h:
#define VIM_VERSION_
On Fri, Nov 03, 2006 at 01:49:24PM +0200, Yakov Lerner wrote:
> Whether Bram thinks it's useful to store this info in some
> v:variable (so script can know it) ?
> Within last year, there were requests how script can know
> whether vim had +NUM option on command line.
>
> Yakov
You mean as i
Yakov Lerner wrote:
> Whether Bram thinks it's useful to store this info in some
> v:variable (so script can know it) ?
> Within last year, there were requests how script can know
> whether vim had +NUM option on command line.
We already have argv() to get the filename arguments. Perhaps there
building vim-7.0.152 on freebsd-4.10 results in warnings about
O_NOFOLLOW being redefined by vim.h. the attached patch fixes
it. i've also compiled with this patch on linux (glibc-2.4),
but nowhere else.
diff -r 8fa2beaad0d3 src/os_unix.h
--- a/src/os_unix.h Fri Nov 03 08:31:12 2006 +
+++ b
Hello,
I am a big fan of the zsh feature allowing to navigate in a
two-dimensional way in matches when completing a command, so I tried to
code something similar in vim. The patch is here :
http://perso.wanadoo.fr/koxinga/cmdline_completion.diff
I am a beginner programmer and not at all fami
