From: Yuan Fu <casouri@gmail.com>
To: Wilhelm Hugo Kirschbaum <wilhelm@floatpays.co.za>
Cc: 58711@debbugs.gnu.org
Subject: bug#58711: Treesit hangs when calling treesit-search-forward
Date: Mon, 24 Oct 2022 13:19:25 -0700 [thread overview]
Message-ID: <106B8822-FE37-4590-BC77-5FB24FB0758C@gmail.com> (raw)
In-Reply-To: <3054006.Zh9iicr411@melissa.local>
>
> Thanks, I would need some time to have a proper look. The reporting issue
> seems to have been fixed. There are some complications to identify the
> appropriate node for defun in elixir as a "call" node might, or might not be
> defun, depending on its child identifier ( i currently have to do a query on
> cycling up the parent ), but will try the respond in more detail in another
> thread.
While fixing the hanging issue, I also improved treesit-beginning-of-defun, which now first goes backward to find a node that matches tresit-defun-type-regexp, then goes upward and finds the top-most parent matching treesit-defun-type-regexp, IOW, it now only stops at top-level defun matches. Does that help with your case?
Yuan
next prev parent reply other threads:[~2022-10-24 20:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-22 9:53 bug#58711: Treesit hangs when calling treesit-search-forward Wilhelm Kirschbaum
2022-10-22 10:26 ` bug#58711: The full tree-sitter parse output Wilhelm Kirschbaum
2022-10-23 6:42 ` bug#58711: Treesit hangs when calling treesit-search-forward Yuan Fu
2022-10-23 23:20 ` Yuan Fu
2022-10-24 17:06 ` Wilhelm Hugo Kirschbaum
2022-10-24 20:19 ` Yuan Fu [this message]
2022-11-10 6:44 ` Wilhelm Kirschbaum
2022-11-10 8:14 ` Yuan Fu
2022-11-10 19:03 ` Wilhelm Kirschbaum
2022-11-10 19:05 ` Wilhelm Kirschbaum
2022-11-10 19:32 ` Wilhelm Kirschbaum
2022-11-10 20:43 ` Wilhelm Kirschbaum
2022-11-10 22:07 ` Yuan Fu
2022-11-11 6:30 ` Wilhelm Kirschbaum
2022-11-14 6:32 ` Wilhelm Kirschbaum
2022-11-14 8:44 ` Yuan Fu
2022-11-14 10:03 ` Wilhelm Kirschbaum
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=106B8822-FE37-4590-BC77-5FB24FB0758C@gmail.com \
--to=casouri@gmail.com \
--cc=58711@debbugs.gnu.org \
--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 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.