bumblebee-status VS polybar

bumblebee-status (github)for bar, hugely modular and uses Python for modules. Nice assortment of included modules, and it's easy to create new ones.

Hmm i think i found a fix for this issue. So the thing is the status bar i use bumblebee-status needs font-awesome. And initially, this was my font configuarion: font pango:FontAwesome, JetBrainsMono Nerd Font 11 and the issue was that, if I was using FontAwesome as well, then the fonts weren't rendered correctly (as shown in the picture) however when I removed it, it worked just fine. And I noticed that two different fonts can be used, one for the bar and one for i3wm itself. Hence I tried that out. So for i3wm's font I had font pango: JetBrainsMono Nerd Font 11 and in the "bar" section I did this:

https://github.com/tobi-wan-kenobi/bumblebee-status << been using this. Works fine for quick and easy setup and go.

I switched to bumblebee-status a few years ago and find it to pretty extensible. Python modules, including lm-sensors support. I have blocks on my bar for radiator push fans rpm, radiator pull fans rpm, both pumps rpm, water in and water out temperatures... as well as a bunch of other stuff like CPU VRM current, package temps, load/usage, etc.

https://i3wm.org/docs/userguide.html#client_colors This is the official page for it. It explains it pretty well. Some people also use https://github.com/tobi-wan-kenobi/bumblebee-status for more color options and themes! Though you might have to point the thing to a custom config file.

Today, in what is still completely unbelievable to me, my small, humble project bumblebee-status reached 1k stars on github. Thank you so much to everyone who uses it or contributes to it, you are awesome! (459 PRs and over 400 opened issues mean that most of the work on this project is anyhow done by the community)

I just patched statuscolors to my dwm build with the aim of bringing colors to my statusbar (I use dwmblocks). I want to achieve something aesthetically similar to bumblebee-status, with each statusbar block appearing in a different color. As explained in the patch documentation, I defined an array of colors in my dwm config, something like this:

bumblebee-status, got some nice themes and info on how to write you own; easy to install too. Check this: https://github.com/tobi-wan-kenobi/bumblebee-status

How about Bumblebee-status or Polybar?" That's a question of preference. Both are excellent.

I'd like to just be able to write a short shell script to check if an exit node is in use, and then pipe that output into polybar which I use anyway. The problem is that I can't find an option in the tailscale Linux CLI client that will show me whether I'm using an exit node or not. Is there a way to do this?

And I follow the step here. https://github.com/polybar/polybar/issues/763

I am on Arch Linux and I am using pywal to generate a colour palette from my wallpaper, which I then use throughout my system. In particular, i have a bash script which grabs these colours and uses them for polybar. The problem is that sometimes these colours do not have enough contrast, and the bar is hard to read. Is there any tool that would allow me to check the readability of my colours, and modify them accordingly, directly from my script? If not, how should I be approaching this issue?

Hello, currently I am trying to get polybar setup on XFCE. I was getting an error along the lines of "background_manager: Failed to copy slice of root pixmap" and according to this GitHub issue, the only solution is to try and set the background another way, like using feh. My only issue now is that it seems like feh isn't actually doing anything whenever I use it to set a wallpaper. I believe this could be because of a conflicting system in XFCE that sets the wallpaper, how can I disable XFCE wallpapers?

Refer to the "Formatting" section of the polybar wiki" (e.g. things like -padding, -margin, -spacing).

As per the docs https://github.com/polybar/polybar/wiki/Configuration it uses a ARGB convention

The short answer is you can't.

There are a few different solutions here, try them out : https://github.com/polybar/polybar/issues/433