Raspberry Pi 4b 4GB - 32 bit OS on USB SSD 256GB - 1360x768 resolution
As one can see in the upper right corner, I have both bspwm and i3 installed.
I tried to add Sway to the mix, got a conflict between lxappearance & lxappearance-gtk3
Is there any work around for this, or is it strictly one or the other?
Thank you. I replaced lxappearance-gtk3 with lxapprearance and Sway then installed.
All three are now working. As long as one doesnāt want to change the theming, it should be OK. However, I donāt know what the consequences will be down the road when some updates come in.
Now I can easily compare the three and make a decision. Right now I am kind of leaning towards Sway just a little.
Thanks everyone for trying out the bspwm config and sharing your views
@OdiousImp Iāll have added a launch script for polybar that will take care of refreshes.
@Shjim I wanted to stick with default keybindings. They are very different form i3wm keybindings. I wouldāve liked to change it, but I just wanted the defaults.
Thank you @Shjim
I donāt want to remove the sys tray, because it shows many useful icons. Like flameshot, minimized applications etc. I will add those on-click scripts.
Edit : @OdiousImp I want to add the click on cpu module to launch a *top application. But afaik we are not bundling any such package as of now. Would you like to add any such package?
I remember a while back joe saying Lxapperance-gtk3 didnāt work on sway so thats why I went with the old one. If it works I can always use the gtk3 one too!
Pacman will not allow both lxappearance and lxappearance-gtk3 to be installed at the same time. If you try, pacman will blow the whistle, call a āconflicting packagesā foul, and ask if you want to replace one or keep the other, but not both.
So we need to keep lxappearance and NOT add lxappearance-gtk3.
So for bspwm we need lxappearance-gtk3.
Sorry! I didnt too as in both. I meant we use the gtk3 one in sway as well. Thats is better one. We want the gtk3 one over the gtk2 right? Ill check the gtk3 one works on sway.
You have me wrong. I no say remove tray just small useful options that good for both users Going trayless no for everyone We all different + there no right or wrong way
@Shjim
It turns out polybar cannot have click events on Cpu/memory modules. To have them clickable, Iāll need to write a script that gives me the output, since text modules are clickable.
Right click on volume module works fine. It opens pavucontrol.