From: Dmitry Gutov <dgutov@yandex.ru>
To: Yuan Fu <casouri@gmail.com>, Juri Linkov <juri@linkov.net>
Cc: bosko.ivanisevic@gmail.com, 62416@debbugs.gnu.org
Subject: bug#62416: 30.0.50; Symbols skipped in the navigation in ruby-ts-mode
Date: Thu, 30 Mar 2023 12:32:26 +0300 [thread overview]
Message-ID: <8fa7abb8-d9ce-e39e-6507-53c52749ac79@yandex.ru> (raw)
In-Reply-To: <F30529E3-3A6A-4B22-8D45-852CCF52B445@gmail.com>
On 30/03/2023 10:47, Yuan Fu wrote:
>> However, there are still a lot of more things that need fixing.
>> When point is on the left curly bracket in
>>
>> b = %Q{This is a "string"}
>>
>> 'C-M-f' doesn't move to the right curly bracket.
>> Also double quotes inside the string are not matched by 'C-M-f'.
>>
>> In
>>
>> d = %(hello (nested) world)
>>
>> 'C-M-f' doesn't move to the closing parens from opening parens.
>
> Have someone fixed these two cases? Because when I tried to invoke
> (treesit-forward-sexp), point moved to the closing bracket/paren.
From which position? When point is right before '{', it doesn't move in
my testing. It does move when it was before '%'.
> Anyway, I just wonder if there’s any fundamental shortcoming with how
> treesit-beginning/end-of-thing works?
I don't know. Seems like this method is good for a lot of things, but
some fiddly details are going to be different from the default forward-sexp.
ruby-mode's sexp navigation is also not ideal in its own way, and it's
been useful anyway.
next prev parent reply other threads:[~2023-03-30 9:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-24 10:24 bug#62416: 30.0.50; Symbols skipped in the navigation in ruby-ts-mode Boško Ivanišević
2023-03-24 18:41 ` Dmitry Gutov
2023-03-25 19:04 ` Juri Linkov
2023-03-26 2:14 ` Dmitry Gutov
2023-03-27 16:29 ` Juri Linkov
2023-03-27 17:28 ` Dmitry Gutov
2023-03-28 6:31 ` Juri Linkov
2023-03-28 22:24 ` Dmitry Gutov
2023-04-03 16:03 ` Juri Linkov
2023-04-03 20:41 ` Dmitry Gutov
2023-03-30 7:47 ` Yuan Fu
2023-03-30 9:32 ` Dmitry Gutov [this message]
2023-04-02 22:34 ` Yuan Fu
2023-04-02 22:43 ` Dmitry Gutov
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=8fa7abb8-d9ce-e39e-6507-53c52749ac79@yandex.ru \
--to=dgutov@yandex.ru \
--cc=62416@debbugs.gnu.org \
--cc=bosko.ivanisevic@gmail.com \
--cc=casouri@gmail.com \
--cc=juri@linkov.net \
/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).