#waybar — Public Fediverse posts

I got an ultrawide monitor for watching those 2.40:1 TV shows.

Joking aside, my setup is almost perfect with an external monitor. #wireplumber seems to be handling the audio, and #niri – the screens, closing the lid, etc. #waybar gives the option to adjust some settings for different monitors while keeping everything else the same.

As an added bonus, having two windows side by side would give you a resolution of almost 1280×1024, which is nostalgic.

#NotFullyLiveVoidPosting #DesktopFriday

I got an ultrawide monitor for watching those 2.40:1 TV shows.

Joking aside, my setup is almost perfect with an external monitor. #wireplumber seems to be handling the audio, and #niri – the screens, closing the lid, etc. #waybar gives the option to adjust some settings for different monitors while keeping everything else the same.

As an added bonus, having two windows side by side would give you a resolution of almost 1280×1024, which is nostalgic.

#NotFullyLiveVoidPosting #DesktopFriday

I got an ultrawide monitor for watching those 2.40:1 TV shows.

Joking aside, my setup is almost perfect with an external monitor. #wireplumber seems to be handling the audio, and #niri – the screens, closing the lid, etc. #waybar gives the option to adjust some settings for different monitors while keeping everything else the same.

As an added bonus, having two windows side by side would give you a resolution of almost 1280×1024, which is nostalgic.

#NotFullyLiveVoidPosting #DesktopFriday

I got an ultrawide monitor for watching those 2.40:1 TV shows.

Joking aside, my setup is almost perfect with an external monitor. #wireplumber seems to be handling the audio, and #niri – the screens, closing the lid, etc. #waybar gives the option to adjust some settings for different monitors while keeping everything else the same.

As an added bonus, having two windows side by side would give you a resolution of almost 1280×1024, which is nostalgic.

#NotFullyLiveVoidPosting #DesktopFriday

I’m switching to the #NotoSans and #NotoSansMono fonts. I think I’m creating the most boring machine possible. Do you see the number of packages? 100. That includes NPM and AppImages.

Another thing I did was set up states in #waybar that hide almost everything until a certain threshold is reached. I don’t need to know if the CPU load, memory use, etc. are below 30%; “call me” when they’re higher.

I also swapped mako for #fuzzel’s relative, #fnott.

#NotFullyLiveVoidPosting #DesktopFriday

I’m switching to the #NotoSans and #NotoSansMono fonts. I think I’m creating the most boring machine possible. Do you see the number of packages? 100. That includes NPM and AppImages.

Another thing I did was set up states in #waybar that hide almost everything until a certain threshold is reached. I don’t need to know if the CPU load, memory use, etc. are below 30%; “call me” when they’re higher.

I also swapped mako for #fuzzel’s relative, #fnott.

#NotFullyLiveVoidPosting #DesktopFriday

I’m switching to the #NotoSans and #NotoSansMono fonts. I think I’m creating the most boring machine possible. Do you see the number of packages? 100. That includes NPM and AppImages.

Another thing I did was set up states in #waybar that hide almost everything until a certain threshold is reached. I don’t need to know if the CPU load, memory use, etc. are below 30%; “call me” when they’re higher.

I also swapped mako for #fuzzel’s relative, #fnott.

#NotFullyLiveVoidPosting #DesktopFriday

I’m switching to the #NotoSans and #NotoSansMono fonts. I think I’m creating the most boring machine possible. Do you see the number of packages? 100. That includes NPM and AppImages.

Another thing I did was set up states in #waybar that hide almost everything until a certain threshold is reached. I don’t need to know if the CPU load, memory use, etc. are below 30%; “call me” when they’re higher.

I also swapped mako for #fuzzel’s relative, #fnott.

#NotFullyLiveVoidPosting #DesktopFriday

Argh, #waybar is so frustrating! On the one hand, you can do some really cool things with it; on the other hand, a third of the options don’t work for no apparent reason.

{bandwidthUpBytesCompact} doesn’t work.
{bandwidthUpBytes:U} doesn’t work.
{%-H} doesn’t work.
"format-en" doesn’t work.
…

Out of 9 modules, 5 are now custom scripts.

Okay, #waybar… I’m not complaining, but I’m baffled by it. It’s as if someone decided #Conky was perfect, just arranging things horizontally was difficult. There are no modern niceties of any kind. Fine, now I have a multi-command script. It checks if the configuration was updated and reloads Waybar. It pulls some custom info. It even renders the clock because displaying the time as “9:30” instead of “09:30” is apparently problematic.

#NotFullyLiveVoidPosting

Okay, #waybar… I’m not complaining, but I’m baffled by it. It’s as if someone decided #Conky was perfect, just arranging things horizontally was difficult. There are no modern niceties of any kind. Fine, now I have a multi-command script. It checks if the configuration was updated and reloads Waybar. It pulls some custom info. It even renders the clock because displaying the time as “9:30” instead of “09:30” is apparently problematic.

#NotFullyLiveVoidPosting

Okay, #waybar… I’m not complaining, but I’m baffled by it. It’s as if someone decided #Conky was perfect, just arranging things horizontally was difficult. There are no modern niceties of any kind. Fine, now I have a multi-command script. It checks if the configuration was updated and reloads Waybar. It pulls some custom info. It even renders the clock because displaying the time as “9:30” instead of “09:30” is apparently problematic.

#NotFullyLiveVoidPosting

Okay, #waybar… I’m not complaining, but I’m baffled by it. It’s as if someone decided #Conky was perfect, just arranging things horizontally was difficult. There are no modern niceties of any kind. Fine, now I have a multi-command script. It checks if the configuration was updated and reloads Waybar. It pulls some custom info. It even renders the clock because displaying the time as “9:30” instead of “09:30” is apparently problematic.

#NotFullyLiveVoidPosting

For reasons, I’ve been neglecting to write about what I’ve been doing. I’ll catch up at some point, at least with the more interesting parts. But, ignoring the “why, ” let me at least explain the “what” (you can play detective and figure out the hardware).

Unsurprisingly, this is #VoidLinux with #niri, #waybar, #mako for notifications, and #fuzzel for the app launcher. Besides browsers and graphics editors, I only have a couple of GUI programs installed.

#NotFullyLiveVoidPosting #DesktopFriday

For reasons, I’ve been neglecting to write about what I’ve been doing. I’ll catch up at some point, at least with the more interesting parts. But, ignoring the “why, ” let me at least explain the “what” (you can play detective and figure out the hardware).

Unsurprisingly, this is #VoidLinux with #niri, #waybar, #mako for notifications, and #fuzzel for the app launcher. Besides browsers and graphics editors, I only have a couple of GUI programs installed.

#NotFullyLiveVoidPosting #DesktopFriday

For reasons, I’ve been neglecting to write about what I’ve been doing. I’ll catch up at some point, at least with the more interesting parts. But, ignoring the “why, ” let me at least explain the “what” (you can play detective and figure out the hardware).

Unsurprisingly, this is #VoidLinux with #niri, #waybar, #mako for notifications, and #fuzzel for the app launcher. Besides browsers and graphics editors, I only have a couple of GUI programs installed.

#NotFullyLiveVoidPosting #DesktopFriday

For reasons, I’ve been neglecting to write about what I’ve been doing. I’ll catch up at some point, at least with the more interesting parts. But, ignoring the “why, ” let me at least explain the “what” (you can play detective and figure out the hardware).

Unsurprisingly, this is #VoidLinux with #niri, #waybar, #mako for notifications, and #fuzzel for the app launcher. Besides browsers and graphics editors, I only have a couple of GUI programs installed.

#NotFullyLiveVoidPosting #DesktopFriday

I'm working on a #waybar #hyprland setup for streaming.

Just added a current_scene indicator - when "privacy" scene is selected, it flashes
It's also shows audio meters and frame drops

So I can rely on my hotkeys to switch the OBS scene and be sure that privacy mode engaged

I is WYSIWYG streaming setup for everyday usage, where I could stream software development/gaming/etc in raw open format

So what I see is exactly what viewers see

#obs #streaming #twitch

I have a #sway and #waybar question for all you #CSS folks.

So I have configure the battery module of the waybar configured. At the top of the file I have the following

#waybar {
background: transparent ;
background-color: alpha(@base, 0.75);
[...]
}

Which makes a nice semi-transparent bar except for...the battery when it is in the warning state, and only during the warning state. Regular and critical state remain semi-transparent, but warning get this ugly black background...

I solved the problem by adding the following lines

#battery.charging {
color: @green;
background: transparent ;
}

#battery.warning:not(.charging) {
color: @yellow;
background: transparent ;
}

#battery.critical:not(.charging) {
color: @red;
}

Notice the critical not changing that does not need background: transparent ;

So I have a working bar, but I really does not know why or how this is giving me a weird behaviour.

Do any one of y'all know what why how where? :battery_full: :battery_medium: :battery_low: :battery_empty:

I have a #sway and #waybar question for all you #CSS folks.

So I have configure the battery module of the waybar configured. At the top of the file I have the following

#waybar {
background: transparent ;
background-color: alpha(@base, 0.75);
[...]
}

Which makes a nice semi-transparent bar except for...the battery when it is in the warning state, and only during the warning state. Regular and critical state remain semi-transparent, but warning get this ugly black background...

I solved the problem by adding the following lines

#battery.charging {
color: @green;
background: transparent ;
}

#battery.warning:not(.charging) {
color: @yellow;
background: transparent ;
}

#battery.critical:not(.charging) {
color: @red;
}

Notice the critical not changing that does not need background: transparent ;

So I have a working bar, but I really does not know why or how this is giving me a weird behaviour.

Do any one of y'all know what why how where? :battery_full: :battery_medium: :battery_low: :battery_empty:

I have a #sway and #waybar question for all you #CSS folks.

So I have configure the battery module of the waybar configured. At the top of the file I have the following

#waybar {
background: transparent ;
background-color: alpha(@base, 0.75);
[...]
}

Which makes a nice semi-transparent bar except for...the battery when it is in the warning state, and only during the warning state. Regular and critical state remain semi-transparent, but warning get this ugly black background...

I solved the problem by adding the following lines

#battery.charging {
color: @green;
background: transparent ;
}

#battery.warning:not(.charging) {
color: @yellow;
background: transparent ;
}

#battery.critical:not(.charging) {
color: @red;
}

Notice the critical not changing that does not need background: transparent ;

So I have a working bar, but I really does not know why or how this is giving me a weird behaviour.

Do any one of y'all know what why how where? :battery_full: :battery_medium: :battery_low: :battery_empty:

I have a #sway and #waybar question for all you #CSS folks.

So I have configure the battery module of the waybar configured. At the top of the file I have the following

#waybar {
background: transparent ;
background-color: alpha(@base, 0.75);
[...]
}

Which makes a nice semi-transparent bar except for...the battery when it is in the warning state, and only during the warning state. Regular and critical state remain semi-transparent, but warning get this ugly black background...

I solved the problem by adding the following lines

#battery.charging {
color: @green;
background: transparent ;
}

#battery.warning:not(.charging) {
color: @yellow;
background: transparent ;
}

#battery.critical:not(.charging) {
color: @red;
}

Notice the critical not changing that does not need background: transparent ;

So I have a working bar, but I really does not know why or how this is giving me a weird behaviour.

Do any one of y'all know what why how where? :battery_full: :battery_medium: :battery_low: :battery_empty:

Blogged : #waybar : simple custom module to help you refocus to your task

https://blog.revathskumar.com/2026/06/waybar-custom-module-to-help-you-refocus.html

Blogged : #waybar : simple custom module to help you refocus to your task

https://blog.revathskumar.com/2026/06/waybar-custom-module-to-help-you-refocus.html

Blogged : #waybar : simple custom module to help you refocus to your task

https://blog.revathskumar.com/2026/06/waybar-custom-module-to-help-you-refocus.html

Blogged : #waybar : simple custom module to help you refocus to your task

https://blog.revathskumar.com/2026/06/waybar-custom-module-to-help-you-refocus.html

Blogged : #waybar : simple custom module to help you refocus to your task

https://blog.revathskumar.com/2026/06/waybar-custom-module-to-help-you-refocus.html

#TIL : You can update the #waybar custom module using signal.

Add `signal: <num>` in the custom module config and update using `pkill -SIGRTMIN+<num> waybar`

It took me a while to figure it out since I was looking in `man waybar` and this is mentioned in `man waybar-custom`.

https://github.com/Alexays/Waybar/wiki/Module:-Custom

#TIL : You can update the #waybar custom module using signal.

Add `signal: <num>` in the custom module config and update using `pkill -SIGRTMIN+<num> waybar`

It took me a while to figure it out since I was looking in `man waybar` and this is mentioned in `man waybar-custom`.

https://github.com/Alexays/Waybar/wiki/Module:-Custom

#TIL : You can update the #waybar custom module using signal.

Add `signal: <num>` in the custom module config and update using `pkill -SIGRTMIN+<num> waybar`

It took me a while to figure it out since I was looking in `man waybar` and this is mentioned in `man waybar-custom`.

https://github.com/Alexays/Waybar/wiki/Module:-Custom

#TIL : You can update the #waybar custom module using signal.

Add `signal: <num>` in the custom module config and update using `pkill -SIGRTMIN+<num> waybar`

It took me a while to figure it out since I was looking in `man waybar` and this is mentioned in `man waybar-custom`.

https://github.com/Alexays/Waybar/wiki/Module:-Custom

A recent update broke my arrow icons in waybar. I use a combination of Font Awesome and Noto Sans for my icons.I needed to change my style.css to use “Noto Sans” to “Noto Sans Mono”.

Ahh... That's better.

A recent update broke my arrow icons in waybar. I use a combination of Font Awesome and Noto Sans for my icons.I needed to change my style.css to use “Noto Sans” to “Noto Sans Mono”.

Ahh... That's better.

A recent update broke my arrow icons in waybar. I use a combination of Font Awesome and Noto Sans for my icons.I needed to change my style.css to use “Noto Sans” to “Noto Sans Mono”.

Ahh... That's better.

A recent update broke my arrow icons in waybar. I use a combination of Font Awesome and Noto Sans for my icons.I needed to change my style.css to use “Noto Sans” to “Noto Sans Mono”.

Ahh... That's better.

I switched from #waybar to #ironbar few months ago. Still, prefer it. Got things out of the box I used scripts for with Waybar. Still, have some problems with some icons, as some can't be centered, right? Hence some are centered and some are left aligned and moving the volume up and down moves the icon right and left. Do you also have this problem?

I switched from #waybar to #ironbar few months ago. Still, prefer it. Got things out of the box I used scripts for with Waybar. Still, have some problems with some icons, as some can't be centered, right? Hence some are centered and some are left aligned and moving the volume up and down moves the icon right and left. Do you also have this problem?

I switched from #waybar to #ironbar few months ago. Still, prefer it. Got things out of the box I used scripts for with Waybar. Still, have some problems with some icons, as some can't be centered, right? Hence some are centered and some are left aligned and moving the volume up and down moves the icon right and left. Do you also have this problem?

Ironbar versus Waybar? Browsing the Arch wiki out of sheer curiosity and procrastination, I stumbled across the ⁠ironbar⁠ package. My PC is currently off, so I cannot test it ... yet. What are the practical differences regarding customisation and resource efficiency?

#archlinux #waybar #wayland #linux #technology #wm

Ironbar versus Waybar? Browsing the Arch wiki out of sheer curiosity and procrastination, I stumbled across the ⁠ironbar⁠ package. My PC is currently off, so I cannot test it ... yet. What are the practical differences regarding customisation and resource efficiency?

#archlinux #waybar #wayland #linux #technology #wm

Ironbar versus Waybar? Browsing the Arch wiki out of sheer curiosity and procrastination, I stumbled across the ⁠ironbar⁠ package. My PC is currently off, so I cannot test it ... yet. What are the practical differences regarding customisation and resource efficiency?

#archlinux #waybar #wayland #linux #technology #wm

Ironbar versus Waybar? Browsing the Arch wiki out of sheer curiosity and procrastination, I stumbled across the ⁠ironbar⁠ package. My PC is currently off, so I cannot test it ... yet. What are the practical differences regarding customisation and resource efficiency?

#archlinux #waybar #wayland #linux #technology #wm

Ironbar versus Waybar? Browsing the Arch wiki out of sheer curiosity and procrastination, I stumbled across the ⁠ironbar⁠ package. My PC is currently off, so I cannot test it ... yet. What are the practical differences regarding customisation and resource efficiency?

#archlinux #waybar #wayland #linux #technology #wm

Hier zwei #wayle repositorys für #opensuse ( #slowroll #tumbleweed ):
https://download.opensuse.org/repositories/home:/yipfluoric/openSUSE_Slowroll/
https://download.opensuse.org/repositories/home:/yipfluoric/openSUSE_Tumbleweed/

Erinnert mehr an #waybar als an eine #quickshell Umgebung. Gibt für Einstellungen sogar eine Gui.

#rust

Wem #quickshell zum Hals raushängt, hier eine interessante Alternative in #gtk4 / #rust
https://github.com/wayle-rs/wayle

#wayle #waybar #windowtiling

Anyone having any success using latest #Waybar in #NixOS? Having switched my #Hyrland to the new Lua config (a painful process, but there is nice power in the Lua config) I'd really like my `hyprland/workspaces` to work.

Anyone having any success using latest #Waybar in #NixOS? Having switched my #Hyrland to the new Lua config (a painful process, but there is nice power in the Lua config) I'd really like my `hyprland/workspaces` to work.

Anyone having any success using latest #Waybar in #NixOS? Having switched my #Hyrland to the new Lua config (a painful process, but there is nice power in the Lua config) I'd really like my `hyprland/workspaces` to work.

Anyone having any success using latest #Waybar in #NixOS? Having switched my #Hyrland to the new Lua config (a painful process, but there is nice power in the Lua config) I'd really like my `hyprland/workspaces` to work.

There's even a "custom" waybar module that supports various triggers/actions defined via JSON. A similar module could be written using mruby that calls DSL methods defined in a Ruby config file.

https://github.com/Alexays/Waybar/blob/master/src/modules/custom.cpp
https://man.archlinux.org/man/waybar-custom.5.en

#freeprojectidea #mruby #waybar

There's even a "custom" waybar module that supports various triggers/actions defined via JSON. A similar module could be written using mruby that calls DSL methods defined in a Ruby config file.

https://github.com/Alexays/Waybar/blob/master/src/modules/custom.cpp
https://man.archlinux.org/man/waybar-custom.5.en

#freeprojectidea #mruby #waybar

There's even a "custom" waybar module that supports various triggers/actions defined via JSON. A similar module could be written using mruby that calls DSL methods defined in a Ruby config file.

https://github.com/Alexays/Waybar/blob/master/src/modules/custom.cpp
https://man.archlinux.org/man/waybar-custom.5.en

#freeprojectidea #mruby #waybar

There's even a "custom" waybar module that supports various triggers/actions defined via JSON. A similar module could be written using mruby that calls DSL methods defined in a Ruby config file.

https://github.com/Alexays/Waybar/blob/master/src/modules/custom.cpp
https://man.archlinux.org/man/waybar-custom.5.en

#freeprojectidea #mruby #waybar

There's even a "custom" waybar module that supports various triggers/actions defined via JSON. A similar module could be written using mruby that calls DSL methods defined in a Ruby config file.

https://github.com/Alexays/Waybar/blob/master/src/modules/custom.cpp
https://man.archlinux.org/man/waybar-custom.5.en

#freeprojectidea #mruby #waybar

Another free project idea: write a generic waybar module that embeds mruby so you could write waybar modules entirely in Ruby.

https://github.com/Alexays/Waybar#readme

#mruby #waybar #wayland #freeprojectidea