vim_dev Google Group

Re: vim homepage: Obsolete reference to http://vi-improved.com/wiki

2010-01-03T17:12:48Z

This isn't the wiki though it once referred to. It seems to be rather
related to the #vim IRC channel, isn't it?

Re: vim homepage: Obsolete reference to http://vi-improved.com/wiki

2010-01-03T17:04:44Z

It should be <[link]>.

vim homepage: Obsolete reference to http://vi-improved.com/wiki

2010-01-03T16:34:56Z

On the vim homepage/community, there is a link to [link]
The domain seems no longer to be active and is now redirected to a
GoDaddy page.
Regards,
Tom

conf check in ftplugin.vim slightly broken (?)

2010-01-03T10:02:47Z

Hey all,
I was having some fun earlier today, going through some .conf files in
Vim and i noticed that conf file that are bind-style (conf filetype in
vim) that use C-style comments like: /* comment */ are not recognized
as the conf filetype (or any other filetype for that matter) and even
when i force the conf filetype on by adding "# comment" to the first

Re: netbeans connection when Vim is not compiled with netbeans_intg

2010-01-02T17:40:51Z

Hi Bram,
I have setup a Mercurial Queues patch at
[link]
It will be easier to test this patch and pyclewn 1.1 can now run with
Vim in a console.
The major change from the patch I sent last April, is that netbeans
version has been increased to "2.5".
Using Mercurial Queues for Vim patches, brings the following advantages:

mousefunc option patch

2010-01-01T21:01:22Z

This will allow scripts to use the statusline and tabline as button click areas.
+ *'mousefunction'* *'mfn'*
+ 'mousefunc' 'mfn' string (default empty)
+ global
+ {not in Vi}
+ When nonempty, this option calls the given function when a mouse click
+ is detected. It expects the function to accept these arguments,

Re: Menu translation & wrong encoding in Windows 7

2010-01-01T13:46:24Z

No problem.
Current language:
"LC_COLLATE=Slovenian_Slovenia .1250;LC_CTYPE=C;LC_MONETARY=S lovenian_Slovenia.1250;LC_NUME RIC=C;LC_TIME=Slovenian_Sloven ia.1250"
BUT!!!
The problem is that, contrary to probably every single UNIX-like
machine, the encoding here doesn't mean "this is the encoding used by

Patch 7.2.325

2009-12-31T13:53:13Z

Patch 7.2.325
Problem: A stray "w" in the startup vimrc file causes the edited file to be
replaced with an empty file. (Stone Kang).
Solution: Do not write a buffer when it has never been loaded.
Files: src/fileio.c
*** ../vim-7.2.324/src/fileio.c 2009-12-02 13:32:10.000000000 +0100
--- src/fileio.c 2009-12-31 14:08:31.000000000 +0100

Patch 7.2.324

2009-12-31T12:18:25Z

Patch 7.2.324
Problem: A negative column argument in setpos() may cause a crash.
Solution: Check for invalid column number. (James Vega)
Files: src/eval.c, src/misc2.c
*** ../vim-7.2.323/src/eval.c 2009-12-24 15:00:31.000000000 +0100
--- src/eval.c 2009-12-31 13:09:19.000000000 +0100
***************

Re: Problem with patch 274

2009-12-31T10:57:19Z

cw is instantaneous for me.
The problem appear only then i'm inserting text at the place of string
"ogoUnitTest", after "class" keyword.
I have the problem when i'm starting vim with vim -u NONE -U NONE and
without any ~/.vim directory, so vim settings are not a part of the problem.
The problem occurs with vim and gvim.

Re: Menu translation & wrong encoding in Windows 7

2009-12-31T04:36:48Z

Hello Mojca,
I'm sorry no one answered your posts in almost one month (or only by
breaking the thread).
To see which locale the OS passes to Vim, load it as
gvim -N -u NONE
and then type
:language
This will show you all parts of the locale: LC_MESSAGES for menus &
messages translations, LC_CTYPE for character encoding, LC_TIME for

Re: vim syntax file patch

2009-12-31T02:48:52Z

Thanks.
I got the version info from my $vimruntime/syntax/vim.vim
seems my version is older.

Re: Problem with patch 274

2009-12-30T19:03:30Z

I'm using Vim-7.2.323 on Linux x86 and for me, going to line 24
in your file ogoUnitTest.php and doing cw command is instantaneous
(24Gcw)
Maybe we have different settings? It would be nice if you could
give the minimal vimrc file which can reproduce the problem
so we can run vim with the same settings using something like:

Problem with patch 274

2009-12-30T17:11:48Z

Hello !
I have a problem with patch 274 about syntax highlighting.
If i'm apply this patch, syntax highlighting become very very very slow
when i'm modifying text in the start of a large fold.
My OS is FreeBSD 7.1-RELEASE-p9.
My vim version (without patch 274) is VIM - Vi IMproved 7.2 (2008 Aug 9,
compiled Dec 30 2009 17:38:06)

Re: vim syntax file patch

2009-12-30T16:50:06Z

I do NOT see this problem, using the 7.2-93 version of the Vim *syntax
script*. I found this version info by looking at the header comment of
$VIMRUNTIME/syntax/vim.vim.
When I paste your code into a new Vim session and :set ft=vim, both
function snippets shown above fold as expected, although the
g:test_foo is highlighted as a VimFunctionError.