Closed Lucho32-byte closed 1 month ago
Does this work as expected if you use set shellslash
in your config?
PS! I really don't like Windows.
PS! I really don't like Windows.
Fair enough xd
Does this work as expected if you use set
shellslash
in your config? It solves the autocompletion problem, but introduces two additional problems:
- I'm afraid this option breaks the use of the term (:te command), since I'm using cmd.exe as default shell.
And the documentation says its meant to be used in unix like shells
In addition, this option breaks mechanisms in other plugins dependent on plenary.path (like telescope).
Does this work as expected if you use set
shellslash
in your config? It solves the autocompletion problem, but introduces two additional problems:
- I'm afraid …
I'm not suggesting it as a solution, I just want to know if setting it fixes the present issue. I guess that my intent was unclear. I understand it will likely cause other problems. So, please, could you check if :set shellescape
will fix the completion related issue?
Sorry, I forgot to answer the original question. Yes, actually it solves the autocompletion:
Thanks. I'm pushing an update that I believe fixes this now; please test and help verify that it indeed fixes the problem.
It works! (I've disabled the shellslash
option)
Thanks for the quick response :D
Great, glad to hear it!
Description
I'm currently using a Windows 10 Laptop (No WSL) but the autocompletion for the following path sources appears to be using backslash "\" instead of "/":
However, [graphics] source seems to be working fine![imagen](https://github.com/lervag/vimtex/assets/68834994/88c7d0cd-19ce-4219-b3c9-d5cf594827ee)
Currently as a workaround I've just modified the lines 478, 483, 504 and 525 from the file
vimtex/autoload/vimtex/complete.vim
with the functionsubstitute
to patch this behaviour:Steps to reproduce
% The problem's with the following commands \input{} \include{} \includepdf{} \includestandalone{}
% This works fine \includegraphics{}
\end{document}