On Saturday, March 19, 2016 at 2:11:21 PM UTC-4, Raymond Ko wrote:
> On Thursday, March 17, 2016 at 10:12:12 AM UTC-4, Raymond Ko wrote:
> > On Thursday, March 17, 2016 at 10:04:40 AM UTC-4, Raymond Ko wrote:
> > > On Thursday, March 17, 2016 at 5:45:26 AM UTC-4, Bram Moolenaar wrote:
> > > > Lilydjwg wrote:
> > > > 
> > > > > On Wed, Mar 16, 2016 at 03:43:06PM +0100, Bram Moolenaar wrote:
> > > > > > 
> > > > > > Kent Sibilev wrote:
> > > > > > 
> > > > > > > On Tuesday, March 15, 2016 at 2:33:55 PM UTC-4, Bram Moolenaar 
> > > > > > > wrote:
> > > > > > > > Patch 7.4.1577
> > > > > > > > Problem:    Cannot pass "dict.Myfunc" around as a partial.
> > > > > > > > Solution:   Create a partial when expected.
> > > > > > > > Files:      src/eval.c, src/testdir/test_partial.vim
> > > > > > > > 
> > > > > > > 
> > > > > > > This change doesn't allow functions like this:
> > > > > > > 
> > > > > > > function! s:cache_clear(...) dict
> > > > > > > 
> > > > > > > function! rails#cache_clear(...)
> > > > > > > 
> > > > > > > to be defined at the same time. Any particular reason for this, 
> > > > > > > cause
> > > > > > > this change breaks vim-rails plugin.
> > > > > > 
> > > > > > The patch should not change anything about what functions you can
> > > > > > define.
> > > > > > 
> > > > > > What is the error?  Can you make a small example that fails?
> > > > > 
> > > > > I get these:
> > > > > 
> > > > > 处理 function 
> > > > > <SNR>30_import[11]..<SNR>30__import[20]..<SNR>30__build_module 时发生错误:
> > > > > 第   14 行:
> > > > > E924: can't have both a "self" dict and a partial: <SNR>30_load
> > > > > Mark: Invalid value type for g:mwPalettes[maximum]
> > > > > 
> > > > > At least two plugins are broken.
> > > > > 
> > > > > One of them is the mark.vim plugin, which does this:
> > > > > 
> > > > > elseif type(g:mwPalettes[g:mwDefaultHighlightingPalette]) == 
> > > > > type(function('tr'))
> > > > > 
> > > > > The left side evaluates to a function ref. The result is 10, not 2.
> > > > > 
> > > > > The other is from an old version of neocomplete, 
> > > > > autoload/vital/_b6a796b.vim. You can view it here:
> > > > > https://github.com/lilydjwg/dotvim/blob/master/autoload/vital/_b6a796b.vim#L144
> > > > > 
> > > > > There are a lot of similar error messages from neocomplete too (both 
> > > > > the
> > > > > version I'm using and the latest version on GitHub).
> > > > 
> > > > Please try the latest patch, hopefully this is fixed now.
> > > > 
> > > > -- 
> > > > Q: Should I clean my house or work on Vim?
> > > > A: Whatever contains more bugs.
> > > > 
> > > >  /// Bram Moolenaar -- [email protected] -- http://www.Moolenaar.net   
> > > > \\\
> > > > ///        sponsor Vim, vote for features -- 
> > > > http://www.Vim.org/sponsor/ \\\
> > > > \\\  an exciting new programming language -- http://www.Zimbu.org       
> > > >  ///
> > > >  \\\            help me help AIDS victims -- http://ICCF-Holland.org    
> > > > ///
> > > 
> > > I upgraded to 1583 and everything works now.
> > > 
> > > Thank you!
> > 
> > Oops spoke too soon :-(
> > Apparently I was using -O3 -flto and that miscompiled Vim and made me think 
> > everything was fixed. Switching splits would segfault Vim.
> > 
> > I downgraded the CFLAGS to just -O and now there are some errors instead of 
> > segfaulting. Unfortunately the error is plugin specific, which is not 
> > helpful.
> > 
> > E116: Invalid arguments for function <SNR>76_defplug
> > line  375:
> 
> I made a new build today with the current changes, and everything seems to 
> work again.
> 
> Thanks!

Okay, after using one plugin incsearch.vim for a period of time, I get this 
error. I think some behavior is still different from before this patch. Tested 
on 1615.

function 
incsearch#_go[5]..<SNR>117_get_input[12]..148[4]..146[1]..162[9]..161[10]..160[23]..159[22]..158[8]..131[2]..186[1]..<SNR>128_call[3]..329[1]..<SNR>162_on_searching[2]..<SNR>162_on_char[26]..<SNR>162_move_cursor[19]..<SNR>120_dictfunction,
 line 1 Vim(let):E724: variable nested too deep for displaying

-- 
-- 
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Raspunde prin e-mail lui