smolbar

smolbar is a smol status command for sway.

milestones

• refresh configurable blocks on signals/intervals
• respond to stop and continue signals
• support click events

installation

smolbar is on crates.io!

$ cargo install --locked smolbar

configuration

smolbar is configured through a TOML file.

if --config is not specified, smolbar looks for the toml configuration file at ~/.config/smolbar/config.toml.

for an example of a configuration, see the examples.

header

the header first sent to sway can be configured in the header table. it inherits all keys from the Header JSON object defined in swaybar-protocol(7).

[header]
cont_signal = 18 # default value
stop_signal = 2  # SIGINT

blocks

there are three scopes which can be used to configure individual blocks. each scope has a level of control over each block's Body: immediate has the highest precedence, then local, then global.

global

the global scope is configured at the root level of the config file.

global also inherits all the keys in the Body JSON object defined in swaybar-protocol(7).

# global
full_text = "u only see this in a block if no other scopes define full_text"

[[block]]
# local
full_text = "never see global full_text"

local

all local blocks are tables in the table array block.

local inherits all other keys from the Body JSON object defined in swaybar-protocol(7).

[[block]]
# this block displays the date, updating every second
command = "date" # assuming date coreutil is in $PATH
prefix = "Date: "
interval = 1

immediate

each line of local::command's standard output is parsed in order as a field of the Body JSON object defined in swaybar-protocol(7).

for example, suppose the following script was a block's command:

# interpreted as `full_text`
echo "amazing status information"

# interpreted as `short_text`
echo "short info"

# interpreted as `color`
echo "#ff0000"

hot swapping

smolbar responds to cont_signal (see swaybar-protocol(7)) by reloading its configuration.

this means that by default, sending smolbar's process SIGCONT will cause it to hot swap its config.

[header]
# cont_signal is 18 (SIGCONT) by default

$ pkill -SIGCONT smolbar
# causes smolbar to reload config

cont_signal is also configurable.

[header]
cont_signal = 10

$ pkill --signal 10 smolbar
# causes smolbar to reload config

note

the header, fundamentally, can't be reconfigured during runtime.

this is because in swaybar-protocol(7), it's only sent once, at the beginning of the status command's process.