Reuben Thomas
Reuben Thomas
I have filed minad/jinx#199 and started using Jinx myself to explore how far we can go on the Emacs side. Certainly Jinx was easy to set up and use.
It is worth considering the interface of `nuspell(1)` to copy for a simplified `enchant(1)`.
Mostly diagnostics, also simple batch-mode checking. As you say, not that useful. But I don't think there's much use for pipe-based checking any more.
> Also, as a design decision, my package doesn't dabble into tokenization questions This is interesting, because I'm not clear that Enchant should be doing this either. While it is...
The problem is that the application will typically also be involved in deciding what is the text that has to be checked, according to non-textual markup. It has to work...
By "all this stuff", I meant that applications requiring spell-checking will already have to work out where word boundaries are, for layout purposes. So it's not a different story, it's...
I have started work on Enchant 3 again. I forgot I had already done a little work on this before, but I'm merging the branch I started last August with...
@curable-online Thanks for your feedback. Note that the functionality I've removed is not terminal-based: unlike ispell, which has an interactive mode, enchant's "interactive" mode only works with other programs. I...
This is not related: custom dictionary support refers to user-installed dictionary files, whereas you're talking about non-standard dictionary tags, which should be supported in Enchant ≥ 2.6.1. Please test with...
Many thanks for this, love that it works automatically!