On Oct 16, 12:31 pm, björn <[email protected]> wrote: [...] > Yeah, I'm aware of this. I have tried to get MacVim to display the > files as they are processed but it is difficult. The problem is that > masses of filenames are output to the drawing routines in a very short > time span and this causes the Vim process to hog the CPU so the data > doesn't get to the frontend to actually be displayed as things are > happening. Instead Vim will spew out all this stuff to draw as the > vimgrep command is running, then once vimgrep is finished (and Vim no > longer hogs the CPU) everything gets flushed to the frontend in one > massive draw command. I've tried to force a flush of the draw queue > as it fills up but it doesn't seem to work too well. I don't really > have any good ideas on how to fix this. > > Björn
In "ordinary" not-for-Mac gvim, when 'verbose' is 0 vimgrep outputs about once every second (at most) the name of the file currently being processed. Is it really that hard to make sure that the "search" comparison routine relinquishes the CPU just often enough to let the display routines have a go at it? Maybe even add a zero-length "sleep" at some point in the loop or something? Of course, when 'verbose' is >=1 there is a lot more stuff being displayed so the problem becomes more complex by some orders of magnitude: normally I run with 'verbose' set to 1 from VimEnter to VimLeave but I've found it useful to prefix vimgrep commands by ": 0verbose ". Best regards, Tony. -- hundred-and-one symptoms of being an internet addict: 194. Your business cards contain your e-mail and home page address. --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_mac" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
