Fix initial null configuration; Fix doc compilation errors
This commit is contained in:
@ -124,8 +124,8 @@ class Bar : public sigc::trackable {
|
|||||||
#endif
|
#endif
|
||||||
std::vector<std::shared_ptr<waybar::AModule>> modules_all_;
|
std::vector<std::shared_ptr<waybar::AModule>> modules_all_;
|
||||||
|
|
||||||
waybar::util::KillSignalAction onSigusr1;
|
waybar::util::KillSignalAction onSigusr1 = util::SIGNALACTION_DEFAULT_SIGUSR1;
|
||||||
waybar::util::KillSignalAction onSigusr2;
|
waybar::util::KillSignalAction onSigusr2 = util::SIGNALACTION_DEFAULT_SIGUSR2;
|
||||||
};
|
};
|
||||||
|
|
||||||
} // namespace waybar
|
} // namespace waybar
|
||||||
|
@ -230,8 +230,8 @@ For example, to toggle the bar programmatically, you can invoke `killall -SIGUSR
|
|||||||
|
|
||||||
## User signal configuration
|
## User signal configuration
|
||||||
|
|
||||||
Config parameters `on_sigusr1` and `on_sigusr2` change what happens when bars receive
|
Config parameters *on_sigusr1* and *on_sigusr2* change what happens when bars receive
|
||||||
`SIGUSR1` and `SIGUSR2` signals.
|
*SIGUSR1* and *SIGUSR2* signals.
|
||||||
|
|
||||||
This means that commands `killall -SIGUSR1 waybar` and `killall -SIGUSR2 waybar`
|
This means that commands `killall -SIGUSR1 waybar` and `killall -SIGUSR2 waybar`
|
||||||
can perform user-configured action.
|
can perform user-configured action.
|
||||||
@ -241,7 +241,7 @@ perform more complex `show`/`hide`/`reload` logic for each instance of Waybar.
|
|||||||
One can find the PID e.g. by doing `pgrep -a waybar` which could then match
|
One can find the PID e.g. by doing `pgrep -a waybar` which could then match
|
||||||
by config name or other parameters.
|
by config name or other parameters.
|
||||||
|
|
||||||
### Kill parameter meanings
|
## Kill parameter meanings
|
||||||
|
|
||||||
*show* Switches state to visible (per bar).
|
*show* Switches state to visible (per bar).
|
||||||
*hide* Switches state to hidden (per bar).
|
*hide* Switches state to hidden (per bar).
|
||||||
|
Reference in New Issue
Block a user