Open The-Compiler opened 1 year ago
The monitor handling of lemonbar is just wrong in some cases. If you run barpyrus 0
or barpyrus 1
, can you check the -g
parameter to lemonbar? The geometry should still be correct, but the panel is shown at the wrong location (e.g. compare -g
of lemonbar with what xwininfo
reports).
The error message for barpyrus 2
seems correct, since there are only monitors 0
and 1
(only the long exception is unfortunate indeed).
Hmm, true! Indeed -g 1920x16+1920+0
and -g 1920x16+0+0
get passed to lemonbar, but both instances draw on the left monitor. Looks like this is https://github.com/LemonBoy/bar/issues/163 probably.
The exception is a bit unfortunate indeed. Should HLWMInput.__call__
perhaps check the herbstclient
exit code and bail out earlier with an exception if it's nonzero? Or are there hlwm commands being called which expect a nonzero exit code?
I'd say __call__
should check the exit code per default. I've implemented the check in 0f78dcd5a2cf0ce715dcdfad5368bd129ce7bc24.
I have three screens:
With that, I'm trying to set up xrandr so that I have my laptop screen, and the portable screen on the left of it, mirroring what people see on the projector. Thus, I run:
which leads to xrandr reporting:
and
hc list_monitors
saying:however, I can't get barpyrus to show up on my laptop screen anymore: When I run either
barpyrus 0
orbarpyrus 1
, the panel shows up on the left USB-C screen (probably picking DisplayPort and HDMI?). When I dobarpyrus 2
, I get: