Re: Reason why dict_unref(-1) is called?
Bjorn Winckler wrote: I received the following report of a crash inside Vim on the MacVim project page: http://code.google.com/p/macvim/issues/detail?id=191 From the stack trace it would seem dict_unref() is called with -1 as argument as a result of garbage being collected (as far as I can tell). It it is probably a bit far fetched to ask, but maybe somebody with a bit more insight into the garbage collecting routines will have an idea as to why this may be happening? There was a patch to the garbage collecor in 7.2.192. Were the patches up to that number included? -- I can't complain, but sometimes I still do. (Joe Walsh) /// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net \\\ ///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\download, build and distribute -- http://www.A-A-P.org/// \\\help me help AIDS victims -- http://ICCF-Holland.org/// --~--~-~--~~~---~--~~ You received this message from the vim_dev maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
Re: Reason why dict_unref(-1) is called?
2009/7/3 Bram Moolenaar b...@moolenaar.net: Bjorn Winckler wrote: I received the following report of a crash inside Vim on the MacVim project page: http://code.google.com/p/macvim/issues/detail?id=191 From the stack trace it would seem dict_unref() is called with -1 as argument as a result of garbage being collected (as far as I can tell). It it is probably a bit far fetched to ask, but maybe somebody with a bit more insight into the garbage collecting routines will have an idea as to why this may be happening? There was a patch to the garbage collecor in 7.2.192. Were the patches up to that number included? It doesn't seem that way: :ver VIM - Vi IMproved 7.2 (2008 Aug 9, compiled Apr 13 2009 18:52:48) MacOS X (unix) version Included patches: 1-148 From what I can tell it may be hard to reproduce this bug (I never managed myself) so it will be difficult to see if 7.2.192 fixes the problem but the next snapshot I build will include this patch. I'll report back if there are any further comments on this issue report after I've released the new snapshot. Björn --~--~-~--~~~---~--~~ You received this message from the vim_dev maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
path completion case sensitivity on unix
Path completion on Windows and Unix are different regarding case sensitivity. Given file './Blah' on Windows, vim command ':e btab' will expand out to ':e Blah'. On Linux it does not expand, even though bash does as I have 'set completion-ignore-case on' in my ~/.inputrc. I would much prefer case insensitive completion on Linux. Ideally vim would honor .inputrc settings. I'd like to offer a patch but the learning curve for the vim source seems rather steep. Any chance of getting this implemented? Or can someone offer some pointers on how to do it myself? Thanks, Thomas Rowe --~--~-~--~~~---~--~~ You received this message from the vim_dev maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
Re: path completion case sensitivity on unix
On Fri, Jul 3, 2009 at 2:28 PM, Thomas Rowe wrote: Path completion on Windows and Unix are different regarding case sensitivity. Given file './Blah' on Windows, vim command ':e btab' will expand out to ':e Blah'. On Linux it does not expand, even though bash does as I have 'set completion-ignore-case on' in my ~/.inputrc. I would much prefer case insensitive completion on Linux. Ideally vim would honor .inputrc settings. I'd like to offer a patch but the learning curve for the vim source seems rather steep. Any chance of getting this implemented? Or can someone offer some pointers on how to do it myself? Vim couldn't possibly obey settings in .inputrc, since it doesn't use readline. As for case-insensitive completion, see this: http://groups.google.com/group/vim_dev/browse_thread/thread/d85208b0b888c5a2/7215a4c95e7637e1 ~Matt --~--~-~--~~~---~--~~ You received this message from the vim_dev maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
