typos VS ltex-ls

There is typos though that takes a bit different of an approach to spell checking. When the default is to ask the user (like in a text editor), a regular spell checker is likely better. typos is more meant for being run in an automated fashion.

I recommend you run https://github.com/crate-ci/typos

Oh yeah, I can see you short hashes being a problem. The challenge has been finding the right heuristic for them

Is there good usage examples for this tool? typos simply traverses directories on invocation, wonder if there's a static analysis equivalent for ltrs.

highly recommend adding https://github.com/crate-ci/typos to your CI...very easy to add to a github action, catch fun spelling errors even in camelCased and snake_cased variable names...catch em before they become public facing APIs

I like to use https://github.com/crate-ci/typos as a command-line option. It's built to run as a service or in CI... I run it in our code review software and it has been a big hit.

there's a little comparison table here https://github.com/crate-ci/typos/blob/master/docs/comparison.md

typos

ltex-ls is huge. I have following setup in Neovim which works excellent. (I use Neovim only as scratchpad)

Hi, folks! There is great language server that provides spell checking for markdown and LTeX files using language tool called ltex-ls. By default there is no ability to use code code actions like Add to dictionary, Hide false positive, and Disable rule in NeoVim since those handlers should be implemented on the client side. So I created a simple plugin to add handlers to those actions and load already saved information on initialization of the server. I had no time to extensively test it yet, but it seems working for me just fine.

I am currently using https://github.com/valentjn/ltex-ls and it is a decent step up.

Nice! I have longed for a rust implementation of ltex-ls.

You can use ltex-ls with an LSP client. It looks like FOSS.

I didn't know about LTEX. It seems like a good option! I will try and the do a comparison of the two. LTeX uses MPL-2.0 license. Which is usually prefered by LaTeX users over Grammarly' proprietary software. How is the CPU usage with LTeX and how has been your experience with it?

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!