blob: c954dbbda68533b5196828a349ab917a7c89090d (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
|
- grep shows treesitter context around
- this could be implemented as a separate binary
- clickable file:lines show somehow (as highlights or something else)
- is line above of below middle one on the editor
- is this on the same file as open on the editor
- clickable things for the mouse should be navigatable with the keyboard
- like if I get some search results I can just use tab to navigate them, the editor should know:
- semantic boundaries (maybe just jump to the next clickable thing?)
|- web: native web client (DOM-rendered, not canvas/WASM). Use WASM only for text logic (parsing, grep, treesitter analysis, look internals) — rendering stays in native DOM/CSS for accessibility, performance, and browser-native text selection. Send structured display commands (layout tree, styled spans, cursor, scroll pos) from WASM to JS via a flat buffer or JSON.
|
