code-debug VS texlab

We will use dap-mode with the dap-gdb-lldb option here. Under the hood, it uses the debug adapter from the Native Debug VSCode extension. Configuring it is described on the dap-mode webpages. After we have configured dap-mode, we could in theory reuse the launch.json configurations from the VSCode related articles above. That will require that you also use lsp-mode, as dap-launch depends on the lsp-workspace-root function and will not resolve when lsp-mode is not used. I don't use lsp-mode with C (company-clang and company-c-headers provide what I need), so the next logical solution would be to create a debug template ourselves:

I'm not sure.

I can see that this extension claims to make debugging with GDB work in VS Code:

https://github.com/WebFreak001/code-debug

and that at least for emacs there exists a project to use that extension:

https://github.com/emacs-lsp/dap-mode/blob/master/dap-gdb-ll...

Not having tried it, I can't speak to how well it works, and I don't know if there are adapters for other editors.

The link at the top of page here, references the github repo : https://github.com/WebFreak001/code-debug which isnt the same thing as installed by vscode or by running dap-gdb-lldb-setup . Indeed this link points to a codebase using .ts files in different locations to the VSCode extension installed .js files. (I did set up the dap program/path variables to use the .ts files but that didnt work)

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!