Open Mr5quid opened 1 year ago
Sorry for the late reply.
Currently the search for pdf file starts from the current directory and loops upwards in directories until it finds a .latexmain
or a .synctex.gz
file and a pdf file with the same basename.
Would it be most useful if the is an out_dir
setting in the plugin or if it's possible to call the SVED_Sync()
function with an argument?
If you want a quick and dirty hack you can take inspiration from this pull request https://github.com/peterbjorgensen/sved/pull/14
Hi,
I'm trying to use SVED to enable forward/backward search between NeoVim running VimTex on one hand and Evince on the other hand. I'm working on a big LaTeX project compiled through
latexmk
with multiple source files that I can compile independently with thesubfiles
package. For the record, I'm usinglualatex
, notpdflatex
. My directory is set up as follows :All build files, including
*synctex.gz
and output pdf get made in thedist
folder in the root directory. The reason why I have twolatexmkrc
files (one in root and one in my Chapters folder) is just because it's a dirty trick I found so that everything always goes into the top leveldist/
folder, whether I'm compilingmain.tex
or an individual chapter (they only differ by their$out_dir
statement, which is a relative path, so one is just'dist'
while the other is'../dist'
).Anyway, backward search works just fine, which is absolutely fantastic (I wish I had found this project sooner). However calling
SVED_Sync()
for forward synchronization returns "Did not find main pdf file". I noticed that if I moved the relevantsynctex.gz
and pdf file in the same folder as the current .tex file I'm compiling, it then works.So my question is : is there a way to make SVED take into account my
out_dir
instructions ? I use either theout_dir
key for thevimtex_compiler_latexmk
dictionary in myinit.vim
or alatexmkrc
instruction (in this case they come from thelatexmkrc
files, but I mean that my vimtex is set up to write everything in./dist
anyway).Thank you !