nvim-typora VS texmagic.nvim

It's far from my best work but nvim-typora has a table creator in it.

nvim-typora

If you use Neovim (I know this is r/vim but it's still relevant), you can try nvim-typora which is a simple plugin to make working with [Typora](typora.io) easier from Neovim. Typora itself is an excellent markdown renderer, and it allows embedded latex inside its documents.

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.