Hi Björn, It did still happen for me in the console version. However, I just did a git pull, jumped form 7.2.245 to 7.2.267 and it's gone away. :-) One thing to note is that console Vim shows the file names (every now and then) being grepped by vimgrep, but MacVim does not show the file names. Thanks for the help. Craig
On Oct 15, 11:11 pm, björn <[email protected]> wrote: > 2009/10/13 Craig: > > > > > I can still reproduce a crash when running vimgrep > > I followed the bug reproducing wiki > > no ~/.vim, ~/.vimrc, ~/.gvimrc > > Mac OS X /native/ vim doesn't reproduce the bug. > > I simply open MacVim > > cd to my code (it doesn't happen if there are no sub directories, so > > it's related to the **/) > > :vimgrep string **/*.rb > > > and bang: > > - snip - > > Craig, > > I cannot reproduce this (I tried ":vimgrep a **/*.c" at the root of > the Vim sources and a couple of similar things) so it must somehow > depend on the folder structure. It seems like a core Vim bug though > so I suggest you post the crash log (not the above debug info) to > vim_dev and you'll maybe get a better response. > > Oh, before you post to vim_dev: can you repro the crash if you start > MacVim in Terminal mode only? (e.g. > "/Applications/MacVim.app/Contents/MacOS/Vim" from Terminal) > > Björn --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_mac" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
