texmagic.nvim VS vimtex

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.

The full changelog is here: https://github.com/lervag/vimtex/releases/tag/v2.14.

Feel free to open an issue on GitHub. Please take care to fill in the issue template; it's meant to help you provide useful details that make it easier for me to give a useful answer.

I use vimwiki almost daily, but it's not professional use, just daily notes and organizing my life. I started using zim but I found I really missed writing/editing with vim. Then I found vimwiki. There are things I'm not super happy about with it. I saw that /u/lervag (love his vimtex plugin) released a wiki plugin and I was/am interested in it, but I have so much in my wiki right now that I don't want to deal with conversion issues.

Definitely get vimtex and set it up so you can view the compiled document in one window, and your notes in the other. Get used to vim a bit with some vim tutorial (there are a bunch out there), and have latex shortcuts you use in all your documents.

I do think VSCode is a great tool and I recommend it frequently to people, but I still want to set the record straight here. Yes, vim is obviously limited in the sense that as a CLI app it doesn't draw it's own PDF or HTML windows, that's fair. But it can remote control your favorite PDF viewer or browser for roughly the same functionality. I'm currently writing my thesis using vimtex and it's quite smooth. And all the other stuff you mention is implemented quite competently by various plugins like vim-fugitive, coc.nvim, vimspector and copilot.vim.

Obsidian is limited by its use of markdown files. You can use Overleaf, Vimtex, or LaTeX workshop on VS Code to render your tex documents.

Some language-specific plugins like vimtex also include their own text objects.

I would post an issue on the VimTeX Github page: https://github.com/lervag/vimtex/issues. That way you might also get help to disable the possible indexing. I have also needed to disable project file scanning to stop Vim from hanging, when pressing Ctrl + N to perform simple auto-complete.

Absolutely VimTeX