[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#60559: 29.0.60; "Cannot activate tree-sitter" spam
From: |
Eli Zaretskii |
Subject: |
bug#60559: 29.0.60; "Cannot activate tree-sitter" spam |
Date: |
Thu, 05 Jan 2023 11:00:31 +0200 |
> 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.
- bug#60559: 29.0.60; "Cannot activate tree-sitter" spam, (continued)
- bug#60559: 29.0.60; "Cannot activate tree-sitter" spam, Eli Zaretskii, 2023/01/05
- bug#60559: 29.0.60; "Cannot activate tree-sitter" spam, Ihor Radchenko, 2023/01/05
- bug#60559: 29.0.60; "Cannot activate tree-sitter" spam, Jostein Kjønigsen, 2023/01/05
- bug#60559: 29.0.60; "Cannot activate tree-sitter" spam, Eli Zaretskii, 2023/01/05
- bug#60559: 29.0.60; "Cannot activate tree-sitter" spam, Jostein Kjønigsen, 2023/01/05
- bug#60559: 29.0.60; "Cannot activate tree-sitter" spam, Gregory Heytings, 2023/01/05
- bug#60559: 29.0.60; "Cannot activate tree-sitter" spam, Gregory Heytings, 2023/01/05
- bug#60559: 29.0.60; "Cannot activate tree-sitter" spam,
Eli Zaretskii <=
- bug#60559: 29.0.60; "Cannot activate tree-sitter" spam, Eli Zaretskii, 2023/01/05
- bug#60559: 29.0.60; "Cannot activate tree-sitter" spam, Dmitry Gutov, 2023/01/05
- bug#60559: 29.0.60; "Cannot activate tree-sitter" spam, Theodor Thornhill, 2023/01/05
bug#60559: 29.0.60; "Cannot activate tree-sitter" spam, Stephen Berman, 2023/01/04
- bug#60559: 29.0.60; "Cannot activate tree-sitter" spam, Eli Zaretskii, 2023/01/04
- bug#60559: 29.0.60; "Cannot activate tree-sitter" spam, Stephen Berman, 2023/01/04
- bug#60559: 29.0.60; "Cannot activate tree-sitter" spam, Eli Zaretskii, 2023/01/05
- bug#60559: 29.0.60; "Cannot activate tree-sitter" spam, Juri Linkov, 2023/01/05
- bug#60559: 29.0.60; "Cannot activate tree-sitter" spam, Eli Zaretskii, 2023/01/05
- bug#60559: 29.0.60; "Cannot activate tree-sitter" spam, Eric Gillespie, 2023/01/06