Michael Davis

Using tree-sitter node names might actually not work out very well since different grammars use different names for the comment nodes (`line_comment`/`block_comment`/`comment`/etc). Instead using a capture like `@comment` could be...

I think something like that should work. It would be on a per-language basis though and I'm not sure how many languages have comment captures. I think it's ok if...

I think it would be good to have an auto-pairs functionality for the block comment tokens, like HTML ``. It wouldn't be reliable for detecting a block comment via tree-sitter...

It would probably be ok in most cases but it would be prone to edge-cases. I would prefer a workaround since I don't use auto-pairs myself but I don't have...

I would prefer splitting the block comments entirely to another PR if possible since that implementation needs some design.

> This breaks the select -> action model since I can't visually confirm what's being deleted. I agree `md` breaks select-then-act but with the proposed command that trims the ends...

`workingDirectory` is not part of the LSP spec - this server is expecting it as a configuration option. You can provide configuration options with the `config` option in `languages.toml` like...

Command modifiers are not supported because they're not supported upstream in crossterm: https://github.com/crossterm-rs/crossterm/issues/389 Support for command could most likely be added with a GUI but otherwise awaits that issue upstream.

Can you please provide descriptions in your issues @taupiqueur? I'm not sure if this is about any current behavior in particular or a general idea to always/never exit select mode

Tree-sitter-scheme is also oddly large (1.5MB), I think because of all of the regexes in the grammar definition. We might be able to support all lisps with one tree-sitter-sexp grammar?