Gokul Soumya

I was initially going to put the debouncing as a TODO, but I could already experience input lag on a release build with `rust-analyzer` as a test case LSP if...

There's `space + /` that does a project wide search, but it isn't interactive yet (#196). Note that it isn't fuzzy since it uses regex.

This is already present in the `Selection manipulation` setion of the docs: https://docs.helix-editor.com/keymap.html#selection-manipulation.

Indent queries will also have to added to the [`indents.scm`][2] file. The tree-sitter node names can be obtained [from the grammar][1]. [1]: https://github.com/tree-sitter/tree-sitter-python/blob/b14614e2144b8f9ee54deed5a24f3c6f51f9ffa8/grammar.js#L277-L296 [2]: https://github.com/helix-editor/helix/blob/master/runtime/queries/python/indents.scm

Maybe something a bit more descriptive like `:character-info`?

Helix draws its own cursors since we need multiple cursors, hiding the terminal cursor.

> would it be possible to have the docs as a comments for the rust functions and then extract it from there? I wanted to do the same for config...

Do you mean split windows inside the editor itself or different terminal windows running separate `hx` instances ? For the latter it would be the responsibility of the window manager...

#1154 uses the terminal cursor, so the cursor becomes hollowed (works on alacritty, kitty, wezterm, etc) which is what I rely on with vim: 

> which you then have to clear with backspace or somesuch, but then pressing enter again to move to a new line adds an indent, which you also have to...