jinx VS esup

jit-spell: Alternative to Flyspell which operates asynchronously and checks the entire screen (not just words you just typed). Similar to u/minad's jinx (which is in fact a fork of jit-spell); jinx runs the spell-checker synchronously inside Emacs via a C module, while jit-spell uses an asynchronous subprocess.

Just use jinx it's dope

Another recent example is my Jinx package, where people suggested that I should rather put the functionality into Ispell or Flyspell. Neither are good places to put the Jinx functionality as a mode. Obviously Jinx is a large enough and self-contained package providing a well-defined feature set. Furthermore its mode of operation is entirely different from both Ispell and Flyspell, so putting it there wouldn't result in much code reuse. It would look more like two packages cramped into one. Sometimes clean alternative implementations are justified.

Thank you! I tried to get it working, but unfortunately it isn't compatible with MacOS. https://github.com/minad/jinx/issues/82

One thing that had improved recently for writing is the appearance of several new spell-checking packages, the most recent and popular one being jinx. Grammar/style checking is still sub-optimal. Not sure if authors rely on such tools or that your Grammar knowledge is such that you don't need it and for really proof-reading you have an editor anyway.

Jinx is the new kid on the block for spell-checking, and it is the best!

I can't help you specifically, but have you looked at Jinx by the formidable Daniel Mendler? Jinx lets you use multiple spell-checking backends (hunspell included) with multiple dictionaries—even in the same file. So, for example, I have used German and English dictionaries simultaneously to edit a mixed-language file.

Wow, interesting that my response is getting down voted. It seems not enough that I give away my work for free. Nevertheless I appreciate support from the community, as other Emacs package developers. The support is actually helpful. To clarify, publishing my configuration would translate into quite a bit of work, requiring separation of private and public bits.

Just want to praise a package called jinx, it provides a spell checker for Emacs, which is really fast.

Probably the best way to figure out what's going on at startup time is ESUP (Emacs Start Up Profiler): https://github.com/jschaf/esup You could run it on the old config and the new. Although I suppose the processes may be different enough that there's nothing meaningful to compare.

I agree with you. For startup profiling, use-package-report and https://github.com/jschaf/esup can help too.

A very useful tool for achieving faster startup is esup (https://github.com/jschaf/esup) which times each code block that runs in the emacs startup.

Have you tried running M-x esup with https://github.com/jschaf/esup to see what is taking up the start-up time?

Are you on Emacs 28? Native-comp is enabled by default and it's Just Worked™ for me. Or are you on at least Emacs 27? Emacs 27 added native JSON parsing; stuff like lsp-mode works a lot better now.

(Personally running Emacs 29 built from source on an M1 Pro; everything is instant! Even on my old dumpy i5 machine, everything except startup was pretty snappy, with the exception of startup which took ~4 seconds.)

If it's startup you're concerned about, try the esup[1] package to figure out what's taking so long.

[1]: https://github.com/jschaf/esup

If you're really interested what happens on startup, you can play around with the startup profiler( https://github.com/jschaf/esup ) or similar packages that time the execution of your .emacs.

I used the Emacs Startup Profiler (ESUP) https://github.com/jschaf/esup which identified several culprits in my init files. Removing or deferring the loading of those packages took my startup time from ~15 seconds to about 2.5 seconds. (Still room for improvement!)

GitHub - jschaf/esup: ESUP - Emacs Start Up Profiler

Try out esup