Configuring texlab for neovim and evince #925
-
I just installed texlab and evince-synctex and set up the following configuration according to the wiki:
For me, autocompletion, diagnostics and build on save work. However, forward search does not seem to work. After the pdf is built, evince does not open (should it?). If I open evince manually, the viewport does not move after the pdf is built. If I call Is there a problem with my config? How can I debug or view more information about the command errors? |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 5 replies
-
I found out that my Fedora toolbox was missing the package
Reverse search does not work, but I guess this a problem with Neovim? |
Beta Was this translation helpful? Give feedback.
-
Does your build finish without errors? Maybe, the error message reported by Neovim is a bit misleading here (
Yes, reverse search needs to be implemented by the editor and the viewer. The LSP server does not have an effect here. |
Beta Was this translation helpful? Give feedback.
-
I guess this is it, thanks. Trying again, the build finishes, the document is fine but neovim reports "Build Error". I can not find any errors in my logfiles and there are no diagnostics for my complex template, but if I try a minimal example
The message is "Build Success". The only other thing I'm missing is support for magic comments to tell texlab to use xelatex for the one project I have that requires it. Otherwise texlab works great for me and I'm very happy with it. :) |
Beta Was this translation helpful? Give feedback.
-
Hey, I am getting the same issue here. Did you ever manage to fix this? |
Beta Was this translation helpful? Give feedback.
I found out that my Fedora toolbox was missing the package
python3-gobject
. With this, forward search works now.:TexlabBuild
does not work, but I don't need it with build on save.Reverse search does not work, but I guess this a problem with Neovim?