Such a behavior most likely is far from one's expectations. Though, there is
no any riddle here, just the latest version of exuberant ctags cannot parse
new extensions to VIM script.
It can't parse function autoload#blah#foo#method, either.
So if you want to include this into your patch,
On 7/10/06, Sean Reifschneider [EMAIL PROTECTED] wrote:
On Mon, Jul 10, 2006 at 07:56:13PM +0300, Yakov Lerner wrote:
Vim is special. I believe that being organic extension of
programmer/sysadmin fingers, it deserves special attitude
that other packages.
By refusing to build vim from sources
Soon-Ping Phang wrote:
I'm trying to determine whether I should submit a bug
report for a problem I encountered or if one was
already submitted.
Basically, I'm finding that if I paste a long line of
text (4650+ characters) into an 80x25 Vim window (v7.0
on WinXP), and then,
Patch 7.0.036
Problem:Can't compile with small features and syntax highlighting or the
diff feature.
Solution: Define LINE_ATTR whenever syntax highlighting or the diff feature
is enabled.
Files: src/screen.c
*** ../vim-7.0.035/src/screen.c Fri May 5 23:13:04
charles--
i have formatoptions set in my .vimrc to tcroqn
i have a script i call gvime that starts 'vim -g -c Explore'
(i tried 'gvim -c Explore' with the same result)
if i run gvime, and select a file to edit, i find
formatoptions is now croqn -- the t has been whacked,
and even with a
On Tue, Jul 11, 2006 at 06:53:23PM -0500, scott wrote:
charles--
i have formatoptions set in my .vimrc to tcroqn
i have a script i call gvime that starts 'vim -g -c Explore'
(i tried 'gvim -c Explore' with the same result)
if i run gvime, and select a file to edit, i find
formatoptions
