From: Ship Mints <shipmints@gmail.com>
To: 73557@debbugs.gnu.org
Subject: bug#73557: c-ts-mode 'emacs-c broken with treesit-load-name-override-list
Date: Sun, 29 Sep 2024 15:29:25 -0400 [thread overview]
Message-ID: <CAN+1HbrW+BMRfkL6fbpq88eJhHeM7_PNgFZB+Y+9s24c1rFSuA@mail.gmail.com> (raw)
In-Reply-To: <CAN+1HbpH=XQvd2uzgneKQd-kp8_r7+zgGj0bTRf67oaArwQbMQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1143 bytes --]
This is on Emacs 29.4. Taking a quick look at master, it seems this hack is
gone.
On Sun, Sep 29, 2024 at 3:09 PM Ship Mints <shipmints@gmail.com> wrote:
> The c-ts-mode "fake" emacs-c grammar does not work in the presence of a 'c
> grammar provided in treesit-load-name-override-list.
>
> For example, I set this override to point to my treesitter c grammar which
> uses the file name "c.dylib" on Mac, not "tree_sitter_c.dylib":
>
> (add-to-list 'treesit-load-name-override-list '(c "c" "tree_sitter_c"))
>
> c-ts-mode says:
> (define-derived-mode c-ts-mode c-ts-base-mode "C"
> ...
> (setf (alist-get 'emacs-c treesit-load-name-override-list)
> '("libtree-sitter-c" "tree_sitter_c"))
>
> I think this code should first look for the 'c grammar in
> 'treesit-load-name-override-list before setting a hard-coded file name that
> may not work for everyone.
>
> I can get around this, temporarily, by setting a symlink from c.dylib to
> libtree-sitter-c.dylib. It took a while to figure out what was going on,
> though. This is surely going to confuse other people.
>
> Thank you,
>
> Stephane
>
[-- Attachment #2: Type: text/html, Size: 2681 bytes --]
next prev parent reply other threads:[~2024-09-29 19:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-29 19:08 bug#73557: c-ts-mode 'emacs-c broken with treesit-load-name-override-list Ship Mints
2024-09-29 19:29 ` Ship Mints [this message]
2024-09-30 11:15 ` Eli Zaretskii
2024-09-30 12:51 ` Ship Mints
2024-09-30 14:10 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAN+1HbrW+BMRfkL6fbpq88eJhHeM7_PNgFZB+Y+9s24c1rFSuA@mail.gmail.com \
--to=shipmints@gmail.com \
--cc=73557@debbugs.gnu.org \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.