1-Setting the path to a recursive path cause that omnicpp is very slow under windows. ex: set path= D:\\** in your _vimrc and you will see.
2- Omnicpp does not work when the name of an object is only one character. ex MyClass E; E-> does not complete. 2 bugs in omnicpp Thanks Best Regards Epanda On 28 avr, 08:52, epanda <[EMAIL PROTECTED]> wrote: > Thanks John, > > I don't think it is the network because the problem "CTRL+X CTRL+O > very slow" happens at my office and at my home PC. > > At the office, there is a local network, at my home I am on internet. > > Concerning the plugin file I will try to locate it with a vimdiff. > > Thanks > Best Regards > > On 24 avr, 12:07, "John Beckett" <[EMAIL PROTECTED]> wrote: > > > epanda wrote: > > > I have done two tests and I have two bugreports.txt but I > > > don't know how to search the difference which make that > > > omnicpp is very slow under windows and fast under virtual > > > Linux CentOS. > > > I believe the idea was that you would compare the two files to try and find > > any > > differences in the configuration of Vim on the two systems. There should > > not be any > > significant speed difference, so you are looking for some config setting > > that might > > be responsible. For example, if one system loaded a particular plugin and > > the other > > didn't, you would be suspicious of that plugin (and might close Vim, move > > the plugin > > file somewhere, then retest). Use vimdiff to compare the files. > > > I can't see how it would apply to your situation, but a common cause of > > stupidly > > slow responses on Windows is some sort of timeout waiting for network > > activity. On > > the Windows machine, at command prompt (cmd.exe), you might enter the > > command 'net > > use' to see if there are any network connections. The ultimate test for > > network > > problems would be to capture traffic with Wireshark or Network Monitor and > > see if > > anything happens when you do your test. > > > John --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
