From: Yuan Fu <casouri@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 70438@debbugs.gnu.org, Stefan Heitmann <sh@bytekomplex.de>
Subject: bug#70438: Emacs error 6 abort when starting rust-ts-mode
Date: Fri, 26 Apr 2024 09:49:01 -0700 [thread overview]
Message-ID: <B1EF2F55-CDC4-46C2-B31A-C46FF1954F18@gmail.com> (raw)
In-Reply-To: <86plud1sxk.fsf@gnu.org>
> On Apr 25, 2024, at 6:19 AM, Eli Zaretskii <eliz@gnu.org> wrote:
>
>> From: Stefan Heitmann <sh@bytekomplex.de>
>> CC: "70438@debbugs.gnu.org" <70438@debbugs.gnu.org>
>> Date: Thu, 25 Apr 2024 11:24:13 +0000
>>
>> Thank you very much for your help...
>>
>> I think I understand roughly the issue and it makes sense that you can't do anything here... But I think, I could file another bug report for the repo maintainer of the arch package 😉
>
> Yes, please.
In the GitHub issue that tracks this incident, the author made clear that maintaining ABI versioning correctly is beyond their ability right now. So I think we should pin the tree-sitter version. But then IIUC we can only bump tree-sitter version with each Emacs release? This is a bit unfortunate but better than crashing Emacs.
This also brings me to the versioning of tree-sitter grammars—they really do change often, we should really consider pinning their version in some way. The current catch-up game we play can’t be scalable.
Yuan
Quote:
>> Just so that this is clear to me: The solution to the immediate problem would be for the relevant Linux distros to issue a new Emacs package?
> I really think that in order to provide a reliable end-user experience, and prevent issue like this, Emacs should just statically link a particular version of Tree-sitter.
> If some Linux distros mandates that all libraries, no matter how small, must be distributed as dynamic libraries (which is just... staggeringly impractical IMO), then the Emacs package should specify a particular version of the Tree-sitter package to use - not a version range.
>> I think we have to commit to not using the semver version in our library names, and to follow libtool-compatible rules for selecting a SONAME instead.
>>
> I agree with this. Ideally, we should set up tooling to automatically bump the soname on breaking ABI changes. But if any Emacs package maintainer is seeing this issue - we do not yet have this tooling - this library is maintained by a small team, and may not have perfect ABI stability! Consider taking a more conservative approach to dependency versioning, so that end users don't have to deal with situations like this!
next prev parent reply other threads:[~2024-04-26 16:49 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-17 11:41 bug#70438: Emacs error 6 abort when starting rust-ts-mode Stefan Heitmann
2024-04-17 16:27 ` Eli Zaretskii
2024-04-20 8:28 ` Yuan Fu
2024-04-20 9:36 ` Eli Zaretskii
2024-04-20 22:20 ` Yuan Fu
2024-04-21 4:47 ` Eli Zaretskii
2024-04-21 23:57 ` Yuan Fu
2024-04-22 5:54 ` Eli Zaretskii
2024-04-22 6:13 ` Yuan Fu
2024-04-22 6:53 ` Eli Zaretskii
2024-04-25 11:24 ` bug#70438: AW: " Stefan Heitmann
2024-04-25 13:19 ` Eli Zaretskii
2024-04-26 16:49 ` Yuan Fu [this message]
2024-04-26 17:21 ` Eli Zaretskii
2024-04-26 17:58 ` Yuan Fu
2024-04-26 18:32 ` Eli Zaretskii
2024-04-27 3:06 ` Yuan Fu
2024-04-27 6:16 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=B1EF2F55-CDC4-46C2-B31A-C46FF1954F18@gmail.com \
--to=casouri@gmail.com \
--cc=70438@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=sh@bytekomplex.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).