From: Eli Zaretskii <eliz@gnu.org>
To: Gregory Heytings <gregory@heytings.org>
Cc: casouri@gmail.com, 60559@debbugs.gnu.org, theo@thornhill.no,
mardani29@yahoo.es, jostein@secure.kjonigsen.net,
monnier@iro.umontreal.ca, larsi@gnus.org, epg@pretzelnet.org
Subject: bug#60559: 29.0.60; "Cannot activate tree-sitter" spam
Date: Thu, 05 Jan 2023 11:00:31 +0200 [thread overview]
Message-ID: <83zgaxwe34.fsf@gnu.org> (raw)
In-Reply-To: <8dea9f3e0ec5d0bfd26b@heytings.org> (message from Gregory Heytings on Thu, 05 Jan 2023 08:48:11 +0000)
> Date: Thu, 05 Jan 2023 08:48:11 +0000
> From: Gregory Heytings <gregory@heytings.org>
> cc: Fu Yuan <casouri@gmail.com>, 60559@debbugs.gnu.org,
> Theodor Thornhill <theo@thornhill.no>, mardani29@yahoo.es,
> Jostein Kjønigsen <jostein@secure.kjonigsen.net>,
> Stefan Monnier <monnier@iro.umontreal.ca>,
> Lars Ingebrigtsen <larsi@gnus.org>, epg@pretzelnet.org
>
> > I suggest a slightly different solution: add a global minor mode, say
> > 'ts-modes'. Users would only have to add (ts-modes 1) in their init
> > files, and the logic would be:
> >
> > (treesit-available-p) ts-modes
> > nil nil => do nothing
> > nil t => warning
> > t nil => use available tree-sitter modes
> > t t => use available tree-sitter modes
> >
> > This seems more future-proof: otherwise users who want to user the
> > available tree-sitter modes would have to require all such modes. ATM
> > there are only 19, but Emacs 30 could very well have twice or thrice
> > that number of tree-sitter modes.
>
> And perhaps we could even add a third value for ts-modes, say "no". In
> that case tree-sitter modes would not be used even if they are available.
> Users may prefer, for one reason or another, to not use them even if they
> are available because their system administrator installed them.
We discussed a minor mode approach, and discovered it doesn't work
well enough, because different modes need different considerations.
Moreover, silently doing something depending on whether
treesit-available-p returns nil is not the best UX, as I explained
up-thread. Actually loading a mode that the user wants is much more
natural and easy.
P.S. Please disregard the previous email about customizing a list: I
was confused when I wrote it.
next prev parent reply other threads:[~2023-01-05 9:00 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-04 14:48 bug#60559: 29.0.60; "Cannot activate tree-sitter" spam Eric Gillespie
2023-01-04 18:36 ` Eli Zaretskii
2023-01-04 19:40 ` Daniel Martín via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-01-04 20:03 ` Eli Zaretskii
2023-01-05 0:43 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-01-05 6:51 ` Eli Zaretskii
2023-01-05 7:06 ` Ihor Radchenko
2023-01-05 7:44 ` Eli Zaretskii
2023-01-05 8:00 ` Ihor Radchenko
2023-01-05 8:26 ` Eli Zaretskii
2023-01-05 8:40 ` Ihor Radchenko
2023-01-05 8:42 ` Ihor Radchenko
2023-01-05 8:54 ` Eli Zaretskii
2023-01-05 8:52 ` Eli Zaretskii
2023-01-05 9:05 ` Ihor Radchenko
2023-01-05 7:57 ` Jostein Kjønigsen
2023-01-05 8:12 ` Eli Zaretskii
2023-01-05 8:32 ` Jostein Kjønigsen
2023-01-05 8:44 ` Gregory Heytings
2023-01-05 8:48 ` Gregory Heytings
2023-01-05 9:00 ` Eli Zaretskii [this message]
2023-01-05 8:56 ` Eli Zaretskii
2023-01-05 13:17 ` Dmitry Gutov
2023-01-05 14:02 ` Theodor Thornhill via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-01-04 19:59 ` Stephen Berman
2023-01-04 20:10 ` Eli Zaretskii
2023-01-04 20:33 ` Stephen Berman
2023-01-05 6:41 ` Eli Zaretskii
2023-01-05 7:46 ` Juri Linkov
2023-01-05 7:58 ` Eli Zaretskii
2023-01-05 14:59 ` Eric Gillespie
2023-01-22 13:24 ` Eli Zaretskii
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=83zgaxwe34.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=60559@debbugs.gnu.org \
--cc=casouri@gmail.com \
--cc=epg@pretzelnet.org \
--cc=gregory@heytings.org \
--cc=jostein@secure.kjonigsen.net \
--cc=larsi@gnus.org \
--cc=mardani29@yahoo.es \
--cc=monnier@iro.umontreal.ca \
--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).