hunspell VS typos

Are you familiar with Hunspell? Dictionaries are comprehensive enough to be part of different Office Suites, so I don't see them as constricted to autocorrect.

You mentioned kinda like a con the online requirement, if you're interested in an offline method, try Hunspell. Otherwise, I just come up with this, is based on Google Suggestions API (even tho is not public):

i prefer and use hunspell

One can implement Huntspell which is what all browsers use (for example when typing in text areas). Is very simple and is C++.

Hunspell-based spell check

Excellent questions. https://github.com/wooorm/dictionaries here are some. The original dataset is here https://github.com/hunspell/hunspell#dictionaries

Since you are using already GPLv3: Why not reusing hunspell dictionaries/wordbooks? https://github.com/hunspell/hunspell

Those questions are open ones—and even the way they can be answered is unclear. Intuitively, Hunspell's suggestions are quite decent—otherwise, it wouldn't be the most widespread spellchecker, after all. A fair amount of "unhappy customers" can be easily found, too, in hunspell's repo issues. At the same time, one should distinguish between different reasons for the sub-par suggestion quality. It might be due to the algorithm itself, or due to the source data quality: the literal absence of the desired suggestion in the dictionary, or lack of aff-file settings that could've guided Hunspell to finding it.

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

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

typos

Check out typos for ideas.

See an example port from assert_cmd to trycmd.

When I was designing the programmatic API for my programmer's spell checker [0], I found that it was easy to get an exit code from something else in the stack and if they all used 1, there wasn't a way to differentiate. This is the reason I went with sysexists, so I would have a more nuanced codes to reduce the probability of two processes in the stack returning confusable errors.

[0] https://github.com/crate-ci/typos

Not sure where you sourced your dictionary but checkout my spell checker comparison for others that have the same model for you. I know I've tested typos dictionary against Python's typeshed and Linux to identify false positives. codespell has quite a large, well maintained dictionary.

> Finally, I have been thinking about how to encourage spell checking within code. I think a better solution would be a terminal command (like Standard) where a user just can run:

Interesting timing since I've been polishing up my source code spell checker in prep for announcing it. I even used the name "typos" because I couldn't find it in use as a CLI.

https://github.com/crate-ci/typos

There are also some other code spell checkers out there: https://github.com/crate-ci/typos/blob/master/docs/compariso...

Here is an example of an Enum from one of my projects: