> I'm not sure what you mean here; in particular, what do > you mean by "scan"? Do you actually mean moving about in > the file?
I believe he's talking about using ^P/^N in insert-mode where it scans (using the 'complete' setting) various other open buffers/windows/files. If one of those other buffers happens to be a huge file, it's a royal pain. E.g. vim honkin_huge_file.txt :e small_file.txt go into insert mode and start typing something followed by ^N or ^P to auto-complete what you typed. Vim will scan honkin_huge_file.txt for completion-matches which can take a fair bit of time based on processor speed, memory (or how much was swapped out), and the file-size. Ideally there would be a way for LargeFile.vim to prevent honkin_huge_file.txt from being scanned. I don't believe there's currently any way for LF.vim to set this per-buffer. -tim --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_use" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
