-
Notifications
You must be signed in to change notification settings - Fork 0
Configuration
Configuration is done with yaml, a human- and machine-friendly markup language.
The config file is located at $XDG_CONFIG_HOME/kherson/config.yml
If the config does not exist or cannot be loaded, the minimal default hardcoded config is used.
Modules:
- ...
- ...
Colors:
- ...
- ...
- Name: time
ForegroundColor: "*green" # default: "*white"
BackgroundColor: "#111111" # default: "*black"
Pre: "⏰ " # default: ""
Post: " " # default: ""
Command: "date"
Args: ["+%d.%m.%Y - %R:%S"] # default: []
Interval: 1 # default: 1
Markup: "none" # default: "none"
Signal: 2 # default: 0
Key that is used by i3bar/swaybar and kherson to identify the blocks.
Possible values: any string
Text color of the block.
Possible values: any color in hex notation (#123456
) / color reference (*red
). If color reference is used, the repective color is loaded from the Colors section.
Background color of the block.
Possible values: see ForegroundColor
String added before the block text.
Possible values: any string.
String added after the block text.
Possible values: any string.
Command that is executed to get the block text. The output lines are read similar to i3blocks:
Block text (full_text)
-ignored-
ForegroundColor
BackgroundColor
Possible values: any executable on your system.
Command-line arguments that are passed to the command.
Possible values: any array of any strings.
How often (in seconds) the command output is re-loaded.
Possible values: any positive integer.
Whether i3bar should format the output using markup.
Possible values: none
/ pango
Number of signal (SIGRTMIN+n
) that can be sent to kherson to reload the block.
Possible values: 1
-15
The colors array is optional, colors are loaded from these locations before (later locations override previous ones):
- Hardcoded defaults (gruvbox dark theme).
- Environment. Any environmental variable that starts with
COLOR_
is considered a color value. Example:$COLOR_RED
is loaded asRED
- Your config