blob: 8c83ab553554dbb48f27e711118d5e4007dbf5dc (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
|
// STATUS: live scratch notes, deliberately unfiled — nothing compiles this file
// (no `build.zig` step, and `docs/design.typ` does not include it); kept because
// the first two ideas are still open. The ideas themselves were last touched in
// change `xmzpwklp` (2026-08-01); this header and the LANDED annotation below
// are 2026-08-26 and changed no idea.
- 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 or below middle one on the editor
- is this on the same file as open on the editor
- LANDED: 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?)
- it is `n`/`N` rather than Tab (Tab is the acme execute chord): a MOTION over
look-able text, not a jump (`Pardes.lookWalk`, `Pardes.lookSpanIn`). Enter —
the look chord — on what a step leaves selected is what opens it.
- the "semantic boundaries" are the pane's GRAIN (`output_pane.Grain`): in free
text the largest whitespace-delimited run `look.resolve` can act on
(`look.lookableSpan`), in a results buffer one stop per ROW
(`look.lookableLineSpan`). Written up in `docs/helix-keys.md`, the `n`/`N`
row of section A.
|
