homelab/stack
1
0
Fork 0
Code Issues 122 Pull Requests 1 Actions Packages Projects 1 Releases Wiki Activity

style(marimo): legible hidden-code peeks and quiet not-yet-run cells

Browse Source 
Notebooks open without auto-run (so they never contend for the DuckDB
write lock), so every cell sat in marimo's needs-run state: a peach
border plus outline from --stale and a yellow-filled run button, and
hidden-code cells showed their two-line peek at 20% opacity — applied
to the wrapper around CodeMirror, out of reach of the existing
opacity override. Now: a brass-tinted hairline (no outline), an
outlined brass run button, and the peek at 0.55. --stale itself is
untouched: marimo also tints stale outputs with it.
This commit is contained in:
kert
2026-10-27 13:39:24 -04:00
parent a2ff945be1
commit ff3d64a978
1 changed files with 21 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

21
assets/css/marimo.css
View File

@@ -396,6 +396,27 @@ body {
opacity: 1 !important;
}
/* Hidden-code cells: marimo shows a two-line peek at 20% opacity on the
wrapper *around* the editor (out of reach of the rule above), which
read as broken grey text. Keep it a quiet peek, but legible. */
.marimo-cell .cm.opacity-20 {
opacity: 0.55 !important;
}
/* Cells that have not run yet (notebooks open without auto-run so they
never contend for the DuckDB write lock): a brass-tinted hairline and
an outlined run button instead of a peach glow and yellow fill. */
.marimo-cell.needs-run {
border-color: color-mix(in srgb, var(--chart-5) 35%, var(--border)) !important;
outline: none !important;
}
.marimo-cell [data-testid="run-button"][class*="yellow-3"] {
background: var(--card) !important;
border-color: var(--chart-5) !important;
color: var(--chart-5) !important;
}
.cm-gutters {
background: var(--secondary) !important;
border-right: 1px solid var(--border) !important;