vimtex VS texlab

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

Helix defaults to texlab so try that?

This is overly verbose and redundant, therefore I disabled eglot-inlay-hints mode in LaTeX and opened and issue: https://github.com/latex-lsp/texlab/issues/858

I have a very limited understanding of Parsing but I would assume that Latex Language Servers have to implement similar parsing too? So maybe check out TexLab. It’s implemented in Rust so maybe it’s an interesting reference.

Is it possible to get a wordcount for LaTeX documents from an LSP like ltex-ls or texlab?

If you’re still stuck you can try reporting an issue here or look for ones similar to yours: https://github.com/latex-lsp/texlab

If you use emacs, I recommend to get some modern goodness by installing lsp-mode (or eglot) to interact with language servers and then install a latex language servers like texlab. This in my expericence really improved the autocompletion so I don't feel like I loose anything over using vscode, texlab or overleaf .Recently I also switched to lsp-ltex for language-tool integration. All those tools lsp servers can also be used from other editors with lsp support, so use what you prefer. I would only recommend emacs to those who want a fully customized and keyboard driven experience and are not afraid to eventually modify some lisp code. But it has its unique advantages, many editing tools and in addition to the still great auctex also cdlatex for super quick math typesetting.

you can use https://github.com/latex-lsp/texlab

I use overleaf these days mostly because overleaf makes it effortless to work across multiple machines. I still have my neovim + texlab [1] setup just in case though.

[1]: https://github.com/latex-lsp/texlab

Story time: I really love Neovim for programming, but one thing I love it even more for is scientific writing. Tools like texlab make this especially fun! But for a well-rounded experience, I need a few more things: (i) Grammar checking. For that I can recommend ltex, an LSP-server which adds LaTeX support to language tool. (ii) Thesaurus lookup. (Neo)vims integrated thesaurus format is a little bit limited. But thankfully 'thesaurusfunc' exists so I could easily write a small plugin to add support for openoffice.org mythes thesauri. (iii) Machine translation. Now we're finally getting to the topic of this post. I write most of my stuff in English but I'm not a native speaker, so machine translation is valuable for me. It can help me to overcome writers block to an extent, for example. There already exist a few plugins for that problem, like vim-translator or translate.nvim. But none of these support interactive modes, a slick UI, and, as far as I know, useful things like motions and counts. This is where my plugin pantran.nvim comes into place! The demo should speak for itself. In the end it was a lot more effort than I anticipated but I'm very pleased with the result. I hope this can be useful to others as well!