Replies: 1 comment
-
I suspect that elixir-mode modifies the syntax table in some way, which changes the treatment of the single quote. However Jinx installs its own syntax table during Jinx operation, see jinx--syntax-table, so this shouldn't be a problem in principle. Maybe Jinx somewhere misses to use jinx--syntax-table somewhere, where it actually should. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm working in
elixir-mode
, and Jinx is highlighting the chunk "shouldn" in "shouldn't" as misspelled. This doesn't happenemacs-lisp-mode
orhaskell-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-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 runeval-buffer
, which should spin up a second Emacs session in a self-contained temporary location.)You can see in the
elixir-mode
buffer that the comment has a misspelling marked undershouldn
inshouldn't
. Any ideas where I could look to fix this?Beta Was this translation helpful? Give feedback.
All reactions