From: Eli Zaretskii <eliz@gnu.org>
To: Yuan Fu <casouri@gmail.com>
Cc: dmitry@gutov.dev, 66988@debbugs.gnu.org, theo@thornhill.no,
loic.lemaitre@gmail.com
Subject: bug#66988: 30.0.50; treesit-forward-sexp not working properly in js-ts-mode and tsx-ts-mode
Date: Wed, 15 Nov 2023 14:19:53 +0200 [thread overview]
Message-ID: <83cywbryxi.fsf@gnu.org> (raw)
In-Reply-To: <1C21FE6B-D54E-4301-AB87-5F15EE06D7D1@gmail.com> (message from Yuan Fu on Tue, 14 Nov 2023 22:28:34 -0800)
> From: Yuan Fu <casouri@gmail.com>
> Date: Tue, 14 Nov 2023 22:28:34 -0800
> Cc: Dmitry Gutov <dmitry@gutov.dev>,
> Theodor Thornhill <theo@thornhill.no>,
> 66988@debbugs.gnu.org,
> loic.lemaitre@gmail.com
>
> > Is it feasible to have a variable that controls whether the full
> > matches are implied in these APIs? Then we could start by making it
> > optional, and at some later time make it the default.
>
> It’s feasible, but I don’t think it’s TRT. The major mode author should have the control over whether the full match is implied, not the user. It doesn’t make sense to toggle the variable either. If you change that variable, major mode code must also change to be correct.
So what do you suggest that we do about this issue?
next prev parent reply other threads:[~2023-11-15 12:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-07 14:56 bug#66988: 30.0.50; treesit-forward-sexp not working properly in js-ts-mode and tsx-ts-mode Loïc Lemaître
2023-11-10 1:41 ` Dmitry Gutov
2023-11-10 7:37 ` Juri Linkov
2023-11-11 2:41 ` Yuan Fu
2023-11-11 7:35 ` Eli Zaretskii
2023-11-15 6:28 ` Yuan Fu
2023-11-15 12:19 ` Eli Zaretskii [this message]
2023-11-18 18:57 ` Yuan Fu
2023-11-19 5:48 ` Eli Zaretskii
2023-11-19 6:19 ` Yuan Fu
2023-11-11 10:49 ` Dmitry Gutov
2023-11-15 6:32 ` Yuan Fu
2023-11-11 15:43 ` Loïc Lemaître
2023-11-11 23:40 ` Dmitry Gutov
2023-11-12 12:10 ` Loïc Lemaître
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=83cywbryxi.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=66988@debbugs.gnu.org \
--cc=casouri@gmail.com \
--cc=dmitry@gutov.dev \
--cc=loic.lemaitre@gmail.com \
--cc=theo@thornhill.no \
/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).