Re: Call for volunteers: add tree-sitter support to major modes

[Visuwesh]

[செவ்வாய் அக்டோபர் 11, 2022] Eli Zaretskii wrote:

>> [...]
>> Besides, HarfBuzz is arguably a system library.  Modern GNU/Linux
>> systems cannot provide text display without it at all.
>
> The same will arguably happen with tree-sitter, once Emacs starts
> using it seriously.
>
> [...]
>
>> we even have builds that do not support it at all.
>
> We will also support a build without tree-sitter.  It will lack
> important features, exactly like builds without the other optional
> libraries lack important features.  But it will allow one to edit
> program source files.

I've read the rest of this thread and understand the argument but how
memory hungry does Emacs get when enabling tree-sitter?  As far as I
vaguely remember from the original tree-sitter inclusion discussion,
tree-sitter used about the same memory as the buffer did for smallish
files.  Even more vaguely, I remember opening xdisp.c with tree-sitter
enabled shot up the memory usage to an unacceptable limit by my
computer's standards.
As someone with a mere 4G of RAM and 4G of swap space, I'm wondering if
enabling tree-sitter will make my laptop even more memory hungry than it
already can be when stressed [1].


[1] This happens when I have a lot of tabs open in Chromium+a handful of
20~100M PDF files opened in Emacs via pdf-tools.