Eli writes:
> Why would it confuse? You also have there stuff like w32-win.el.gz,
> which is used only on MS-Windows, and other files that are not
> necessarily for your configuration. This is not a problem, and
> shouldn't be one.
I don't know, maybe for me there is a difference between the OS specific stuff, tree-sitter and other stuff in Emacs:
tree-sitter modes 'compete' with 'regular' modes and if I don't have tree-sitter activated at compile time, it can be misleading to see those files there and 'sub-optimal' (to say the least) to get a message that you can't use them.
OS related stuff is different in the sense that, well, if I'm on a Linux system and try to use (you say the OS)-specific features, it is natural that I get a 'wake-up' message there and stop trying to do things that make no sense.
As for the rest, having dormant features that _work_ (or are WIP with a level of maturity enough to be in master) and only wait for me to test them and activate them if they help me in my day-to-day interactions with Emacs, of course, put 10^n n->infinity of those in Emacs, no problem.
In that sense, if there was a way to disregard *-ts-*.el files in ELC/ELN compilation and installation when I compile Emacs _without_ tree-sitter support, the whole picture would be (once again, IMvHO) much more coherent.
Thanks for your patience, /PA