polybar VS wayfire

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

One of the developers just responded on the github issue referecing this thread.

"After a bit of discussion on HackerNews, I got a bit better understanding of the actual problem. People don't want to just configure the keys according to a particular layout - the actual 'issue' here is that they expect the key binding changes together with the layout. Unfortunately, the 0.8.0 changes didn't make this possible to implement as a plugin.

I would reconsider adding this as an option if there are enough interested people. React with a thumbs up to this comment if you are interested in having this option (though the defaults will certainly remain as they are now). Please, react only if you actually use Wayfire or would use it if it had this feature :)"

https://github.com/WayfireWM/wayfire/issues/1601#issuecommen...

I have been on Wayfire for over a year now, and I can't possibly praise it enough. It's entirely modular, so you can make it look and behave exactly as you want. It does tiling, it does Compiz-style wobbly windows and 3D desktop cubes, configurable rules and hotkeys, everything. It's stable and handles gaming flawlessly.

Your impression of Wayland is going to be very much determined by the quality of the compositor implementing it, and I've found Wayfire to be the best, by far - but oddly, also the one least talked about. Everybody's paying attention to stuff like Hyprland, Sway and Mutter - you're barking up the wrong tree there. Wayfire is fantastic, has most of the bells and whistles Compiz on X11 has, and is as pretty or as functional as you want it to be.

- VR support

I thought so too not long ago, but Wayland compositors needed some time to mature, and some of them are getting pretty damn good. Ever since I discovered Wayfire I'm a total believer, it's better than any X window management solution I've used. Much lighter too.

might be a small window when wayfire releases a version, before master identfies as the next release number. (see: https://github.com/WayfireWM/wayfire/blob/master/meson.build )

it lives on as a Wayland compositor