digestif VS texmagic.nvim

1) I believe as a neovim user you have LSP configured, than try digestif. Note: it does not have builtin lspconfig configuration, adding support for digestif is an excercise for the reader ;) Here is some help: lspconfig contribution section

AUCTeX and cdlatex are tried and tested packages in supporting the composition of TeX-documents. However, with the advent of LSP-servers, like TexLab and digestif, there is another (viable?) option to compose TeX-documents.

I’ve tried to follow instructions from digestif (https://github.com/astoff/digestif) but it didn’t work.

The Digestif language server simulates the TeX parsing in a reasonably accurate way, and internally it computes a kind of parse tree. But it doesn't implement all of the LSP editing features, even though this should be a comparatively easy part of the story.

FWIW, the Digestif language server (https://github.com/astoff/digestif) also supports amsrefs.

If you go the LSP route, just FYI, I have a small plug-in called TeXMagic that enhances the functionality of TexLab in one particular way: currently with TexLab you must specify a build engine globally and must edit this global build engine every time you need a different build engine for a different project. My plug-in will help you define any number of arbitrarily-named build engines that you can call in a magic comment (e.g. %! TEX program = dvipspdf) and will pass your requested build engine to TexLab if you point the build key in the TexLab lspconfig table to the global variable my plug-in initializes.

Hi! I made a small plug-in a while ago to augment a small bit of Texlab’s functionality (pass info from magic comments into Texlab’s compiler config settings). Is this functionality something you’d be interested in including in your plug-in? (See https://github.com/jakewvincent/texmagic.nvim)

I wrote this because I had started setting up my workflow in Neovim 0.5.0 and wanted to use the TexLab LSP server with Neovim's LSP client. TexLab has a build service but only provides for a single user-defined build engine (without hacks). TeXMagic.nvim provides a global variable with which you can value the build key in your TexLab config. The variable references a table which is selected by finding the program/build engine name (provided in a magic comment) in either the default latexmk build engines (pdflatex, xelatex, or dvipspdf) or a user-defined build engine.