Ok.
Bram, If anyone don't object to this changes, please check and include.
https://gist.github.com/1280464
diff -r 409691084d19 src/eval.c
--- a/src/eval.c Tue Oct 04 21:22:44 2011 +0200
+++ b/src/eval.c Wed Oct 12 15:41:53 2011 +0900
@@ -21735,6 +21735,9 @@
++hi;
fp = HI2UF(hi);
+ if (
On Oct 10, 2011, at 5:41 PM, erik wrote:
> May I ask for volunteers for testing again.
This is very close.
It definitely fixes issues I reported the last time.
There is a regression bug in handling this:
if (!(attr in urls))
value = escape_txt_chars(value)
# mor
There are a handful of syntax files that use backslash continuation
characters without ensuring that cpoptions is missing C, so when running
vim in vi compatibility mode (such as when there's no .vimrc), you'll get
errors like
Error detected while processing /usr/share/vim/vim73/syntax/po.vim:
On Mon, 10 Oct 2011, mattn wrote:
Thanks for all in this thread.
I still don't assent that vim show functions in complete candidates.
And I wonder why they use ":echo " to get candidate from completion.
I'm thinking who want to know SID are very minorities. And as Ingo
Karkat says, is the c
CC-ing vim-dev
On Tue, October 11, 2011 10:01 am, sinbad wrote:
> On Oct 11, 11:07 am, Christian Brabandt wrote:
>>
>> Thanks for the detailed steps. Next time, please attach the plugin, so I
>> don't have to fix all the linebreaks ;)
>>
>> Unfortunately, I can't reproduce the error. I even tried