Re: Detecting tree-sitter based major-modes for end-user customization and third party functions/packages

[Eli Zaretskii]

> Date: Tue, 20 Dec 2022 12:35:57 +0100
> From: Jostein Kjønigsen <jostein@secure.kjonigsen.net>
> 
> While as a major-mode author, I can decide to use tree-sitter to implement 
> key functionality, we don't expect
> end-users to (need to) have the same level awareness about the technology 
> used to implement the modes
> they are consuming.
> 
> However end-users often want to customize Emacs based on major-mode agnostic 
> properties of the current
> major-mode none the less. Examples are adding hooks for prog-mode, 
> c-mode-common-mode (from
> cc-mode), etc. This may also apply to other third-party packages, in how they 
> interact with buffers (if
> prog-mode do this, if text-mode do that, etc).
> 
> I expect these kinda of needs to arise for tree-sitter based major-modes 
> sooner rather than later, where one
> may be able to leverage tree-sitter node-manipulation functions rather than 
> use text-based equivalents.
> 
> But to be able to leverage tree-sitter based functions, one would first need 
> to know that one is interacting with
> a tree-sitter based major-mode. And to customize one, one would need a hook.
> 
> So how do we plan to expose this to end-users and other developers?

We already have a discussion about this, here:

  https://lists.gnu.org/archive/html/emacs-devel/2022-12/msg00822.html

So just chime in there.