TildaZ Config

One TOML config shape, one muscle memory.

Config paths differ by platform, but the schema stays familiar. Move between Linux, macOS, and Windows with the same mental model for shell, hotkey, font, theme, opacity, and geometry.

Read CONFIG.md Install TildaZ
Portable Ideas

The settings feel the same everywhere.

The config file location follows each OS, but the concepts stay consistent across platforms.

  • shell for the child process
  • hotkey for show / hide
  • theme and font settings
  • opacity, size, position, and scrollback
Example (Linux) 
hotkey           = "F1"
shell            = "/bin/bash"
auto_start       = true
hidden_start     = false
theme            = "Tilda"
max_scroll_lines = 10000

[window]
dock_position   = "top"
width_percent   = 50.0
height_percent  = 100.0
offset_percent  = 100.0
opacity_percent = 100.0

[font]
family            = "DejaVu Sans Mono"
glyph_fallback    = ["Noto Sans CJK KR", "Noto Color Emoji"]
size_point        = 15
cell_width_ratio  = 1.0
line_height_ratio = 1.1

# plus [input] and [keys] -- see CONFIG.md

These are the Linux defaults. A key you leave out uses its default, and TildaZ lists it in a startup notice. shell and the fonts you name must exist on the system. The first launch writes your $SHELL; on macOS and Windows the default fonts differ, and Windows uses cmd.exe. See CONFIG.md for every field and the built-in theme names.

Paths

Same schema, native locations.

PlatformConfig path
Linux$XDG_CONFIG_HOME/tildaz/config_N.toml
macOS$XDG_CONFIG_HOME/tildaz/config_N.toml
Windows%APPDATA%\tildaz\config_N.toml

XDG_CONFIG_HOME defaults to ~/.config. Empty or relative values use that default.

The first launch creates config_0.toml. When every configured instance is already running, launch TildaZ again, press a new hotkey, and choose Create. Each numbered config owns one process, hotkey, and log.