Wrong screen geometry when using xrandr's `--same-as` about barpyrus HOT 3 OPEN

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).

from barpyrus.

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 LemonBoy/bar#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?

from barpyrus.

I'd say __call__ should check the exit code per default. I've implemented the check in 0f78dcd.

from barpyrus.