zathura compatibility with latexmk setting

[chakravala]

On arch linux using latest vim/gvim.

When I launch vimtex, this is my command for it in .bashrc

alias vimtex='vim --servername vim'

the configuration is .vimrc

let g:vimtex_view_method = 'zathura'

This configuration works fine for me, except that when I launch it and press \ll for the first time, zathura is opened and the document is displayed in its previous configuration and then the program freezes for a few seconds, and then it resets the display on zathura with the horizontal scroll reset and a bunch of view settings reset.

However, if I add this to .vimrc

let g:vimtex_compiler_progname = 'latexmk'

then the issue goes away and when I press \ll the zathura imediately displays the document and does not freeze for a few seconds and does not reset my view settings or horizontal scroll config.

However now with this setting I can no longer ctrl+click on zathura to communicate back to vimtex where on what line I want the editing cursor to be placed.

How can I make this work using this option? There's probably some simple thing I am overlooking.

Thanks for any assistance.

[lervag]

First,

let g:vimtex_compiler_progname = 'latexmk'

does not make any sense. This option is meant to define the name/path to the proper Vim executable for doing remote server/client calls during callbacks.

[chakravala]

Then why is it that when I use

let g:vimtex_compiler_progname = 'latexmk'

this solves the issue with zathura resetting my view settings, but I don't really understand what's going on with it. then what is the setting that is supposed to be used for it? the actual text I enter here doesn't seem to make a difference, but as long as I enable this it sovles the zathura issue, but it then causes the issue with the inverse search back to vim.

[lervag]

Ok, since .latexmkrc is not relevant I'm removing all mentions of it from the thread.

I'm thinking the reason it solves the issue is because the default of g:vimtex_compiler_progname is the full path to gvim, which starts with C:\Program Files. The problem here is related to escaping during the callbacks from latexmk.

Could you please update the original post to better match the issue template?

[chakravala]

Okay, seems you already removed it from the post. I'm on arch linux, using the latest vim/gvim, I'm not sure what additional information to provide, since the other settings I use don't affect this issue.

Could you explain more about the escaping during callbacks from latexmk?

[lervag]

Ok, so: Please provide a minimal working example, that is, a minimal vimrc file, a minimal latex file, and the steps to reproduce.

An example:

1. minivimrc:

   set nocompatible
   let &rtp  = '~/.vim/bundle/vimtex,' . &rtp
   let &rtp .= ',~/.vim/bundle/vimtex/after'
   filetype plugin indent on
   syntax enable
   
   let g:vimtex_view_method = 'zathura'

2. A minimal .tex file:

   \documentclass{minimal}
   \begin{document}
   
   Hello World!
   
   \end{document}

3. Now do vim --servername VIM -u minivimrc mwe.tex.

4. Do \ll

   • expect: some behaviour
   • observe: some other behaviour

[lervag]

btw, sorry for mistaking that you were on Windows. Your issue is probably something else. But it is crucial that you describe it in enough detail that I might reproduce it.

[chakravala]

Yes, I created the example files, and it reproduces my issue, and if you change the g:vimtex_compiler_progname it loads the zathura without resetting as described above.

Since this is related to the flickering issue I had before, I'm guessing you are not able to reproduce it

Is my zathura configuration at all relevant?

set synctex true
set synctex-editor-command "vim --servername VIM --remote-silent +%2<Enter>zz %1"

[chakravala]

Okay, well it seems if I put

let g:vimtex_compiler_progname = '/usr/bin/vim`

Then it gives me the same result as completely omitting that setting, so it's equivalent to default

[chakravala]

What happens is that the VIM screen goes completely blank for a few seconds, using the default setting, and then when it finishes processing (not sure what is processing), it redraws the screen and then resets the document view for zathura. This doesn't occur if I change the compiler_progname to something invalid (then the PDF is immediately displayed and vim never goes blank), but zathura is still able to update when I make changes in vim, the only issue it causes is that zathura is no longer able to communicate back the position to vim.

[lervag]

Ok, thanks. I'm pushing some test files now, and the commit should appear in this thread. Please review the test files and confirm that they represent your minimal example.

Also, please give me the output of \li after you have opened a tex file.

[lervag]

So, I'm curious, what happens if you remove the set synctex-editor line (or comment it out) from the zathurarc file.

Also, it would help if I understood what exactly is happening. As you probably understand, I can't reproduce your issue (at least I don't think so). Perhaps it is possible to take a screenshot or screencast?

[chakravala]

I have emailed you screenshots now, and the set synctex-editor does not affect the issue outcome

[lervag]

Ok, I've looked through the screenshots.

Could you check if the problem persists if you set the following option?

let g:vimtex_compiler_latexmk = { 
      \  'callback' : 0,
      \}

Note, please try this with the default g:vimtex_compiler_progname.