Use "pre-cache" for omni-completion in Windows.

[habamax]

Is your feature request related to a problem? Please describe it.

Initial or after :VimtexClearCache ALL omni-completion is quite slow in Windows.

Describe the solution you'd like
It would be nice to pre-cache omni-completion values in background job once file is opened.

Describe alternatives you've considered
None.

Additional context
See #2195

[lervag]

First, some additional context from #2195:

What do you mean here? "save under other path/name"?

:w ~/docs/anotherpath/anothername.tex then switch to it and do all the same

Does this mean that you only have this particular problem in one path, but not in another path?

---

You propose a solution for the issue, but I'm not fully convinced that is necessary. And in any case, I would strongly prefer to first fully understand the actual problem. For that, it would be very nice to have a minimal example.

Essentially, this issue is a duplicate of #1885. And I believe the problem is somehow related to a slowness in calling system('kpsewhich ...'). As such, I would be very interested in looking into this more pointedly. To do that, we first need a proper minimal example.

So, I was hoping I could ask you to make a minimal _vimrc file with something lik the following content:

" Either this (proper minimalism)
set nocompatible
set runtimepath^=/path/to/bundle/vimtex
filetype plugin indent on
syntax enable

" Or, if you prefer to use a plugin manager, e.g.
call plug#begin(...)
Plug 'lervag/vimtex'
call plug#end()

" Relevant VimTeX options follow here

And then also a minimal LaTeX example. You could use your current files, but it would be much better to simplify as much as possible. E.g. start with

\documentclass{article}
\usepackage{natbib}

\begin{document}

\cite{xxx}

\bibliography{...}

\end{document}

Of course, adapt the above enough to reproduce the original problem. And finally, please provide the exact necessary steps to reproduce.

[habamax]

Does this mean that you only have this particular problem in one path, but not in another path?

I did not test it for many cases, there was only observation that for one "old" tex file it takes longer than for the same content file saved to another folder.

[habamax]

You propose a solution for the issue, but I'm not fully convinced that is necessary.

Sure, it was just a guess it might improve UX of windows users but it is no way something I urge you to do :).

And in any case, I would strongly prefer to first fully understand the actual problem. For that, it would be very nice to have a minimal example.

The problem is usual for vim on windows for external process communication. It is the same issue with fugitive which is many times slower on windows.

[habamax]

Will try minimal vimrc and minimal latex tomorrow and let you know.

[lervag]

Great, thanks. Note, perhaps there is an issue with the paths, e.g. bad handling of paths with spaces or something. It could also explain the delay and why it seems to work in a different path. So it would be worth looking into, I think.

[habamax]

Sorry for delllaaaay. :)

I tried it with a minimal document and min vimrc -- initial delay is sub 2 seconds. Maybe 1 second.

Then I tried with my document which has quite a few packages -- it takes about 5-6 seconds (after VimtexClearCache ALL).

So I think this is minor and could be closed.

[lervag]

Ok, I'm glad to hear you find this to be minor. And since I don't see how to improve this further, I agree we keep this closed for now. If you should ever have a good idea for improving this, feel very free to suggest it!