One store in [[cloud.connections]]. Names and pointers only: a secret comes from the
environment variable named here, never from the config file itself.
Color configuration for the application theme: one slot per role, each a name
("cyan", "default"), "#rrggbb" or "indexed(N)". The option registry
documents every slot and holds its dark and light defaults.
[glyphs]: per-slot overrides laid over the Unicode set, so a font that has
more than the coverage floor gets to use it — ☁ back for the object-store
mark, a Nerd Font icon for a checkbox. Keys are the slot names in
glyphs.rs; values keep the display width of the glyph they replace.
Overrides never touch the ASCII set, which stays the tested floor. Layered
like every section: defaults, then each import, then the user’s file.
The variables that name an S3 endpoint, in the order they are consulted. The AWS
SDKs read the service-specific one first, then the general one; AWS_ENDPOINT is
what object_store accepts.
Style of the column cursor’s header and of the current cell: the cell_cursor
tint in bold, or reversed video where the tint would not show, so the cell is
marked on any terminal.
Style of the column cursor’s cells: the column_cursor tint, or nothing where the
tint would not show; the header and the current cell still mark the column there.
path with a leading ~ expanded, and nothing else. For a path from the command
line: cmd, and PowerShell before 7.4, pass ~\data\a.csv on as typed, as every
shell does a quoted "~/a.csv". A $ there has been through the shell already
and is part of a name. A path that is there as typed, such as a file named ~ in
the working directory, is that path.
Whether id can name a source: lowercase letters, digits and -, starting with a
letter or digit, at most 40 characters. It goes into URLs and cache keys, so
nothing that needs escaping is allowed in.
Whether a tint can be told from the terminal’s own background: a 16-color terminal
turns the default tints into black or white, and NO_COLOR into none.
The line after a config file’s mistake: how to get going again. An import that
is not there is skipped, and datui config init writes a root file only where
there is none.