Jason Franklin wrote:

> I appreciate it Bram!
> 
> > Thanks for the verbose explanation.
> 
> I hope not too verbose. :/ I was just being thorough since the bug left me 
> quite confused at first!
> 
> > Another way to fix it is to use "firstwin" in f_gettabvar() when "tp" is
> > "curtab".  curtab->tp_firstwin is not guaranteed to be valid.  To be on
> > the safe side, we can do both.
> 
> I have seen this check used in "evalfunc.c" in several places.  It seems like 
> a good idea. I added a commit to the branch in my fork that does this. It can 
> be found at the following link:
> 
> https://github.com/lifecrisis/vim/commit/7cc4bd69c59c894bd14072ceb2582edfca8a6b9f
> 
> Would you prefer that I open a new patch or just leave it for now?

I'm not quite sure why that check for tp_firstwin being NULL was there.
It doesn't hurt to keep it.

-- 
hundred-and-one symptoms of being an internet addict:
225. You sign up for free subscriptions for all the computer magazines

 /// 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    ///

-- 
-- 
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