From: Stefan Kangas <stefankangas@gmail.com>
To: Wilhelm H Kirschbaum <wilhelm@floatpays.co.za>
Cc: Yuan Fu <casouri@gmail.com>, 60251@debbugs.gnu.org
Subject: bug#60251: 29.0.60; Consider the language at point for tree sitter treesit-inspect-node-at-point
Date: Tue, 5 Sep 2023 16:32:12 -0700 [thread overview]
Message-ID: <CADwFkmndn+8qA9z=q-fNRJ7wxdP3pB90iRJWhoZJZnu37YQh2A@mail.gmail.com> (raw)
In-Reply-To: <87lemzes0b.fsf@gmail.com> (Wilhelm H. Kirschbaum's message of "Thu, 22 Dec 2022 10:42:03 +0200")
Wilhelm H Kirschbaum <wilhelm@floatpays.co.za> writes:
> The following change will make it possible to inspect a node when using
> an embedded language, otherwise it will assume the first specified
> language without allowing specifying the language. This assumes that
> treesit-language-at-point-function has been correctly set. diff --git
Yuan, do you have any comments on the below patch? Thanks in advance.
> a/lisp/treesit.el b/lisp/treesit.el
> index 6407669118..74dfd26776 100644
> --- a/lisp/treesit.el
> +++ b/lisp/treesit.el
> @@ -1931,7 +1931,7 @@ treesit-inspect-node-at-point
> (interactive "p")
> ;; NODE-LIST contains all the node that starts at point.
> (let* ((node-list
> - (cl-loop for node = (treesit-node-at (point))
> + (cl-loop for node = (treesit-node-at (point) (treesit-language-at
> (point)))
> then (treesit-node-parent node)
> while node
> if (eq (treesit-node-start node)
>
>
> Another option might be to allow parser-or-lang as an argument, but
> thinking that as an interactive function for debugging the above might
> be more useful, but either way it does not seem possible to
> inspect-node-at-point for multiple language configuration.
>
> Regards,
> Wilhelm
prev parent reply other threads:[~2023-09-05 23:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-22 8:42 bug#60251: 29.0.60; Consider the language at point for tree sitter treesit-inspect-node-at-point Wilhelm H Kirschbaum
2023-09-05 23:32 ` Stefan Kangas [this message]
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='CADwFkmndn+8qA9z=q-fNRJ7wxdP3pB90iRJWhoZJZnu37YQh2A@mail.gmail.com' \
--to=stefankangas@gmail.com \
--cc=60251@debbugs.gnu.org \
--cc=casouri@gmail.com \
--cc=wilhelm@floatpays.co.za \
/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).