Closed patrickt closed 3 years ago
The only reason that I can imagine is because I am doing some work on
tree-sitter
andtree-sitter-haskell
themselves, and installed new versions of these yesterday. But I’m totally baffled as to why Emacs/emacs-tree-sitter would even be trying to load a module associated with Haskell, since it’s not a part of thetree-sitter-langs
repository.
The default value of tree-sitter-load-path
contains the directory used by the tree-sitter
CLI tool.
The behavior that I’m observing is that if I have a Haskell file open and invoke
tree-sitter-hl-mode
, or if I invokeglobal-tree-sitter-mode
before opening a Haskell file, Emacs crashes hard.
ABI compatibility is currently not checked upon loading. This is a bug. (It doesn't affect tree-sitter-langs
.) There will be a fix to refuse loading languages with incompatible ABI.
There are 2 possible workarounds:
tree-sitter-load-path
.haskell
from tree-sitter-major-mode-language-alist
. (tree-sitter-langs
should probably not add entries for languages it does not provide into this list.)
Hey there 👋🏻 I’ve run into a very strange Emacs behavior today (like all great problems, it didn’t happen yesterday), and I’m hoping I can get some advice on how to debug this. I’m running on macOS 10.15.7.
The behavior that I’m observing is that if I have a Haskell file open and invoke
tree-sitter-hl-mode
, or if I invokeglobal-tree-sitter-mode
before opening a Haskell file, Emacs crashes hard. The only clue in the backtrace is entries abouttsc_dyn::lang::__emr_O__load_language::h08e753d0334bf627
andtsc_dyn::lang::__emrs_E__load_language::extern_lambda::heef5b3dac0575512
:I’ve tried reinstalling
tree-sitter
, switching betweennative-comp
andmaster
Emacs, recompiling Emacs, deleting myelpa/
directories in~/.config/emacs
— no luck. My workaround for this is to avoid invokingglobal-tree-sitter-mode
, instead invokingtree-sitter-hl-mode
when entering non-Haskell files.The only reason that I can imagine is because I am doing some work on
tree-sitter
andtree-sitter-haskell
themselves, and installed new versions of these yesterday. But I’m totally baffled as to why Emacs/emacs-tree-sitter would even be trying to load a module associated with Haskell, since it’s not a part of thetree-sitter-langs
repository. If anyone has seen behavior similar to this, or knows of an effective way to debug crashes that are occurring in this fashion (since the crash is happening outside Emacs,debug-on-error
isn’t useful), I’d be deeply grateful—and thank you all for the amazing work that you’ve done withemacs-tree-sitter
so far!