I've been using vim7.3 for some time, and find some problem with its
ruby support.
1. $curbuf.number always returns 0 on my platform. See this thread for
more infomation
https://groups.google.com/group/vim_use/browse_thread/thread/a122376e8dbc6d29
Later I modified Lusty-explorer to not
On Sep 10, 10:22 pm, Benjamin Fritz fritzophre...@gmail.com wrote:
Unfortunately, I could not find a list of widely supported charsets,
so I just used all the ones in Vim and the IANA registry, as mentioned
previously. If there is such a list, would it be a good idea to limit
the
On Sep 5, 3:33 am, Peter Odding pe...@peterodding.com wrote:
The regex is a 77 KB monstrosity that's supposed to match a predefined
set of strings in 2html.vim output and is complicated by the fact that
it also matches strings with embedded HTML tags. The regex is corrupt
because of a bug in
Ответ на сообщение «Re: 2html.vim causes Vim to crash with a SIGSEGV?!»,
присланное в 20:09:39 11 сентября 2010, Суббота,
отправитель Carlo:
Confirmed, but before crashing it prints
Error detected while processing command line:
E339: Pattern too long
Command:
LANG=C vim -u NONE -c
I believe I've got a patch for this (see below).
First, if you look at the stacktrace in some detail in gdb, you'll see
that this error occurs while matching regexp .* against the current
filename ( in this case) during autocmd execution. The crash occurs
because in line 4730, 'next' is null. In
Hi Carlo,
I can confirm that the much simpler regex you posted also crashes Vim
(in the same way) and that your patch fixes the segmentation fault.
Thanks for taking the time to look into this and posting your patch!
Cheers,
- Peter Odding
--
You received this message from the vim_dev
Peter Odding peter at peterodding.com writes:
The regex is a 77 KB monstrosity that's supposed to match a predefined
set of strings in 2html.vim output and is complicated by the fact that
it also matches strings with embedded HTML tags. The regex is corrupt
because of a bug in my
