From e68c8f5ff1e3892add1bf4e240634ad33a154c84 Mon Sep 17 00:00:00 2001 From: jao Date: Tue, 8 Feb 2022 00:21:51 +0000 Subject: Documentation bits and version bump --- readme.org | 20 ++++++++++++++++---- 1 file changed, 16 insertions(+), 4 deletions(-) (limited to 'readme.org') diff --git a/readme.org b/readme.org index a4f4f9e..179063e 100644 --- a/readme.org +++ b/readme.org @@ -126,13 +126,14 @@ xmobar -TPlain /path/to/config & #+end_src - Other options are ~Ansi~ and ~Pango~. + Other options are ~Ansi~, ~Pango~, and ~Swaybar~. -*** Using xmobar in Wayland with swaybar +*** Using xmobar in Wayland with swaybar or waybar In text mode, xmobar can be told to ouput its information using - pango markup for colors, and it that way you can use it with - swaybar. Here's a minimal ~bar~ configuration for sway's + pango markup for colors and fonts, and it that way you can use it + with swaybar or waybar, if you don't have actions or boxes in your + template. Here's a minimal ~bar~ configuration for sway's configuration file: #+begin_src conf @@ -142,6 +143,17 @@ } #+end_src + In case you want to use boxes around text or click actions in your + template, you can use instead the format ~Swaybar~, which supports + both. This output format follows the JSON /swaybar-protocol/ + defined by swaybar. Configure it simply with: + + #+begin_src conf + bar { + status_command xmobar -TSwaybar + } + #+end_src + * Configuration and further Links - If you want to jump straight into configuring xmobar, head over to the -- cgit v1.2.3