From: Juri Linkov <juri@linkov.net>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: "Boško Ivanišević" <bosko.ivanisevic@gmail.com>, 62416@debbugs.gnu.org
Subject: bug#62416: 30.0.50; Symbols skipped in the navigation in ruby-ts-mode
Date: Sat, 25 Mar 2023 21:04:52 +0200 [thread overview]
Message-ID: <86v8iomzk3.fsf@mail.linkov.net> (raw)
In-Reply-To: <9cfb677e-2c3b-94f3-e09f-8b231dd9b8f5@yandex.ru> (Dmitry Gutov's message of "Fri, 24 Mar 2023 20:41:23 +0200")
>> Navigating word forward/backward skips the Ruby symbol in the ruby-ts-mode.
>> Adding "simple_symbol" to the treesit-sexp-type-regexp is fixing it.
>> (setq-local treesit-sexp-type-regexp
>> (regexp-opt '("class"
>> "module"
>> "method"
>> "argument_list"
>> "array"
>> "hash"
>> "parenthesized_statements"
>> "if"
>> "case"
>> "when"
>> "block"
>> "do_block"
>> "begin"
>> "binary"
>> "simple_symbol" ;; <-- missing
>> "assignment")))
>
> Juri, what do you think?
>
> In the context of your previous feedback regarding sexp navigation in
> ruby-ts-mode.
This is fine. But anyway I think in its current state
treesit-sexp-type-regexp is underdesigned as noted in
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=62238#59
so no tweaking could fix its design flaws. For example,
foo = {
a: b
}
when point is on the left curly bracket, 'C-M-f C-M-b' doesn't
move back to the original position, etc.
next prev parent reply other threads:[~2023-03-25 19:04 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 [this message]
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
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=86v8iomzk3.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=62416@debbugs.gnu.org \
--cc=bosko.ivanisevic@gmail.com \
--cc=dgutov@yandex.ru \
/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).