On Thu, Apr 2, 2020 at 9:09 AM Christian Brabandt <cbli...@256bit.org> wrote: > > [I did not receive the original mail, so answering to Tonys mail, please > keep the list on CC] > > On Mi, 01 Apr 2020, Tony Mechelynck wrote: > > > > Yes, the tags file is sorted and vim is built with +tag_binary and > > > 'tagbsearch' is on. The tags file wasn't case-folded sorted, but I tried > > > with that too and I see similar performance. > > > > > > Anyway, just to remove any potential confusion, jumping to tags via > > > 'CTRL-]' is blazing fast. So is listing all alternatives with 'g]'. Does > > > ccomplete use the same mechanism for searching tags file as those two? > > > If so, then I wonder why it is so much slower. > > Hm, I had a quick look at ccomplete.vim. It not only does a tag search, > but also searches the current file and more importantly, it might call > :vimgrep and :vimgrep is known to be slow if many files have to be > searched. Not sure if there is anything to improve, perhaps adding a > switch to only do tag completion would already help? > > Anyhow, first please create a vimscript profile, so we can exactly see > when it is slow. See :h :profile and this stackoverflow answer: > https://stackoverflow.com/a/12216578/789222
…and note that the :profile command requires the +profile feature, normally excluded at compile-time except in Huge builds. > > Perhaps this can share some more light on the slowness. > > Thanks, > Christian > -- > Dieser Satz beinhalten drei Fehller. Best regards, Tony. -- -- You received this message from the "vim_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/CAJkCKXuOC94GNUab%3DJgvso%3Dixhes_%3Dd1B1iwCwczKm3bhYf49w%40mail.gmail.com.
