zprf render
From Zacess Profile v0.2.2. Edit this page on GitHub
Write config files for a target from a profile that passes its checks.
zprf render --target <TARGET> --out <OUT> <PROFILE>render writes <OUT>/<target>/ from the templates. It only ever writes inside the folder given
to --out and never edits an app's real config. A profile that fails a pair is refused with
nothing written.
Options
| Option | Does |
|---|---|
<PROFILE> |
The profile to render |
-t, --target <TARGET> |
A target from list-targets or all |
-o, --out <OUT> |
The directory to write into. Each target gets its own folder inside it |
-h, --help |
Print help |
Exit codes
| Code | When |
|---|---|
| 0 | The files were written |
| 2 | The profile is invalid, cannot be completed or fails a pair, with nothing written |
Examples
Write every target for a starter profile:
zprf render profiles/zacess-deep-contrast-dark.toml --target all --out ./buildwrote ./build/ghostty/zacess-deep-contrast-dark
wrote ./build/kitty/zacess-deep-contrast-dark.conf
wrote ./build/wezterm/zacess-deep-contrast-dark.lua
wrote ./build/alacritty/zacess-deep-contrast-dark.toml
wrote ./build/tmux/zacess-deep-contrast-dark.tmux.conf
wrote ./build/neovim/colors/zacess-deep-contrast-dark.lua
wrote ./build/vscode/zacess-deep-contrast-dark.settings.jsonWrite one target:
zprf render profiles/zacess-deep-contrast-dark.toml --target kitty --out ./buildWhat each target sets is on the targets page and how to load each file is on the load in each app page.