New architecture

[mickeynp]

New architecture

[mickeynp]

These are all valid points, Damien. Thank you taking the time to writing this out.

Right now, my main interest is experimenting with the ergonomics of tree-sitter-aware semantic tools. I will indeed split out (and remove) dependencies to third-party libs as I never wanted to thrust those on people; they're there right now for no other reason than to test what is possible --- combulate's just an alpha prototype, and it's got more important issues than those right now to tackle than MVC.

Namely:

1. Having to build and maintain sparse trees of 'interesting' nodes. This is slow.
2. Dealing with the complexities around whether point is intersecting the right node. If point is to the right of <foo/>-!- (for example) it's effectively outside it, and detecting adjacency without interval trees (which I've also experimented with, but are hard to keep in sync with TS without reinventing the whole thing) or another datastructure that is quick to check for adjacency due to the sluggish performance of having to walk the tree to check every time.
   This is a serious issue, actually, because node spans are just the length of their syntactic unit, notwithstanding generalised ones that might span a whole semantic class of things, like a whole function or a class.
   Consider:

def foo():
    print("foo")
    -!-

Point is at module and not inside a function. Technically correct.... but unhelpful. You could nav backward until you encounter a non-whitespace char and then back once more --- I did this with an experimental indentation engine I wrote for Python using TS -- but that brings a whole host of awkward corner cases along with it.

3. How can I extend Emacs's builtin navigation and editing facilities in a way that is mostly transparent and builds on what's already there with additional semantic and syntactic awareness

4. Handling undo, and dealing with the tree sitter parse tree going out of sync with the buffer text during buffer changes made in elisp.