all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@linkov.net>
To: Vincenzo Pupillo <v.pupillo@gmail.com>
Cc: Yuan Fu <casouri@gmail.com>, 75456@debbugs.gnu.org
Subject: bug#75456: 31.0.50; Cannot find the definition of the predicate in `treesit-thing-settings'" sexp-list)
Date: Thu, 09 Jan 2025 20:10:28 +0200	[thread overview]
Message-ID: <87msfzvox7.fsf@mail.linkov.net> (raw)
In-Reply-To: <2719520.lGaqSPkdTl@3-191.divsi.unimi.it> (Vincenzo Pupillo's message of "Thu, 09 Jan 2025 10:49:44 +0100")

> Ciao, 
> this problem occurs with js-ts-mode when jsdoc is enabled. Occurs when you 
> place the cursor in a comment highlighted by jsdoc.
> This is the error message:
>
> "treesit-show-paren-data--categorize: peculiar error: ("Cannot find the 
> definition of the predicate in `treesit-thing-settings'" sexp-list)"

Recently I fixed bug#75198 and tested it on your mhtml-ts-mode
where it works nicely, and (treesit-language-at (point))
returns e.g. 'css' on embedded css.

However, now I discovered that (treesit-language-at (point))
returns 'javascript' on embedded jsdoc parts of a js file.

I wonder is this intended?

Since 'treesit-node-match-p' uses node's parser, I could use
(treesit-parser-language (treesit-node-parser (treesit-node-at (point))))
that returns 'jsdoc'.

But first I'd like to know why treesit-language-at doesn't return the same?





  reply	other threads:[~2025-01-09 18:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-09  9:49 bug#75456: 31.0.50; Cannot find the definition of the predicate in `treesit-thing-settings'" sexp-list) Vincenzo Pupillo
2025-01-09 18:10 ` Juri Linkov [this message]
2025-01-09 22:42   ` Vincenzo Pupillo
2025-01-10  3:23     ` Yuan Fu

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=87msfzvox7.fsf@mail.linkov.net \
    --to=juri@linkov.net \
    --cc=75456@debbugs.gnu.org \
    --cc=casouri@gmail.com \
    --cc=v.pupillo@gmail.com \
    /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.