I'm working in elixir-mode, and Jinx is highlighting the chunk "shouldn" in "shouldn't" as misspelled. This doesn't happen emacs-lisp-mode or haskell-mode, so it's probably a problem in elixir-mode. I would love a pointer of where to look to see if I can fix this.
Here's an elpaca-test expression that highlights the error: (I dunno if you're using Elpaca or not. If you are, you should be able to drop the below code in a buffer and run eval-buffer, which should spin up a second Emacs session in a self-contained temporary location.)
;; -*- lexical-binding: t; -*-
(elpaca-test
:interactive t
:early-init
(setq byte-compile-warnings '(not obsolete))
(setq inhibit-startup-screen t)
:init
(load-theme 'modus-vivendi :no-confirm)
(elpaca jinx)
(elpaca elixir-mode)
(elpaca-wait)
(let ((buff (generate-new-buffer "Bug example")))
(set-buffer buff)
(elixir-mode)
(jinx-mode)
(insert "# this is an elixir comment that shouldn't have a spelling error here")
(display-buffer buff))
(use-package jinx
:defer t
:hook ((text-mode . jinx-mode)
(prog-mode . jinx-mode))
:bind (("C-;" . jinx-correct))
:custom
(jinx-camel-modes '(prog-mode))
(jinx-delay 0.1)))
You can see in the elixir-mode buffer that the comment has a misspelling marked under shouldn in shouldn't. Any ideas where I could look to fix this?
I'm working in
elixir-mode, and Jinx is highlighting the chunk "shouldn" in "shouldn't" as misspelled. This doesn't happenemacs-lisp-modeorhaskell-mode, so it's probably a problem inelixir-mode. I would love a pointer of where to look to see if I can fix this.Here's an
elpaca-testexpression that highlights the error: (I dunno if you're using Elpaca or not. If you are, you should be able to drop the below code in a buffer and runeval-buffer, which should spin up a second Emacs session in a self-contained temporary location.)You can see in the
elixir-modebuffer that the comment has a misspelling marked undershouldninshouldn't. Any ideas where I could look to fix this?