New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
emacs-tree-sitter has issues with auto-yasnippet: wrong-type-argument char-or-string-p nil #51
Comments
This seems to be one of the edge cases in Emacs's change tracking mechanism, where the to-be-changed range passed to Can you provide more details to reproduce/debug it? For example:
|
I can't lend the python file due to it being part of a commercial software
project, instead I will try to reproduce on the same machine with a minimal
example, just give me a couple of hours.
El vie., 10 de jul. de 2020 a la(s) 08:52, Tuấn-Anh Nguyễn (
notifications@github.com) escribió:
… This seems to be one of the edge cases in Emacs's change tracking
mechanism, where the to-be-changed range passed to before-change-functions
is empty, but the before-change-text's length passed to
after-change-functions is non-zero (106).
Can you provide more details to reproduce/debug it? For example:
- The Python file.
- The snippet being used (and maybe yasnippet's config).
- Steps to trigger the behavior. For example, any navigation/editing
after opening the file.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#51 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAIBT4CXE2MVHR3M4QQV7J3R24TL3ANCNFSM4OWAXXZA>
.
|
I ran a session of debugging with elisp bug hunter and this is the results:
confusing to say at least lol. I cannot reproduce this bug on my GNU/Linux machine running Emacs 28 tho. I will try to reproduce with a minimal conf and see what happens |
Cannot reproduce on my GNU/Linux machine with Emacs 26. Maybe this is isolated to macOS somehow |
I just reproduced this bug on my GNU/Linux machine:
|
re-compiled my Emacs (version 28.x) and since I can trigger this bug in my GNU/Linux machine I came with a snippet that triggers the issue, after that if I save the modified file Emacs have an exception:
any pointers on how to get more information of this core dump? |
indeed, @ubolonton, I'm having troubles narrowing what is causing this issue in my configuration. I was able to reproduce 10/10 times the error with the following snippet:
I have deleted a bunch of unused packages in my configuration https://github.com/shackra/emacs |
I've updated some packages on my end:
and seems like the issue is gone now. I'll re-open this issue if happens again. these are the commits I have for some of those packages before updating shackra/emacs@6ad8e87 |
After creating a snippet, when I expand the snippet in a Python buffer, I got this error:
the result is that the string is expanded, but those parts with
$1
are empty.My Emacs version:
GNU Emacs 26.3 (build 1, x86_64-apple-darwin18.2.0, NS appkit-1671.20 Version 10.14.3 (Build 18D109)) of 2019-09-02
The text was updated successfully, but these errors were encountered: