summaryrefslogtreecommitdiff
path: root/src/web/pardes.css
diff options
context:
space:
mode:
authorGabriel Schneider <[email protected]>2026-09-24 09:49:23 -0300
committerGabriel Schneider <[email protected]>2026-10-01 00:12:14 -0300
commita3ebcd08f9fb44d5e69ddafae238f83905ff5ba4 (patch)
tree8dc24727e13dd9cb34bec6c3af0dd2434d39c58d /src/web/pardes.css
parenta39fb20cb770c3adb911cec7d1f3d033669ed1bb (diff)
downloadpardes-a3ebcd08f9fb44d5e69ddafae238f83905ff5ba4.tar.gz
pardes-a3ebcd08f9fb44d5e69ddafae238f83905ff5ba4.zip
Paint a prompt on its notice band, not on the body grid
A builtin that asks for input (Save's path, a search, a pipe) shows its prompt as a notice chip, like Msg output and the leader chord. Messages and the chord went through a tag layer, which is what gives a chip the tagline's height, pitch and band offset; the prompt alone stayed on the grid so its caret could sit on a cell. A pixel shell therefore drew its tagline glyphs one to a BODY cell, spaced out like a banner, while the chips around it were set tight. The prompt is now a band like the others and carries its caret on the layer, at the same place in the text the grid pass puts it. The grid still paints it, for terminal clients. What a band says comes from one place, noticeText, which the grid pass and the layer pass both read, and what a prompt says from one place, Pane.promptText, which collectNotices, the painters and submitSearch share. Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
Diffstat (limited to 'src/web/pardes.css')
0 files changed, 0 insertions, 0 deletions