Re: [PATCH 3/6] Disable sfdump if there is no xrandr support.

Jeremie Courreges-Anglas <[email protected]> Sat, 26 Nov 2016 16:15:36 +0100
Newsgroups gmane.comp.window-managers.ratpoison.devel
Message-ID <[email protected]>
Mathieu OTHACEHE <[email protected]> writes:

> Without xrandr support, sfdump command has no interest.

I think this is headed in the wrong direction.  There is no reason to
disable this command when we can easily deal with the single available
screen.

Same thing for your sselect and srestore diffs.  Moreover, those
introduce additional uses of xrandr-specific function in generic code.
I'd rather have a generic abstraction for available screens.

I have to think more about this.

-- 
jca | PGP : 0x1524E7EE / 5135 92C1 AD36 5293 2BDF  DDCC 0DFA 74AE 1524 E7EE

_______________________________________________
Ratpoison-devel mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/ratpoison-devel
signature.asc (application/pgp-signature, 800 B)
-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJYOacYAAoJEA36dK4VJOfuT8QP/0rICbtmF++7TcGYcWWvwHpe
TpNqKRKX2DaQNNljK+L+SpbduUAjQrjgwBGOMYyvgiMsqk3NSrYDs4evu6eNunLR
Uk62bf1Q8gJG6K/AFTZ187/SiXaBINXslxzh+/+0+B1Lj9hopCrVSXPxDPCiwPKG
WzKkQ8ImulF0AAPOO3Rc8j/uo9maSDb+u9g5hAE+ofsu5JyDqZrRwSQYLODdMb3p
K4nYYKaJ6X1LqK+hrFsEpcs1/kMxWLqDyY7ToJ/isdIFMoec5+1wq9rJULl8Xbl4
mMcUHly4AER6e4VZMFoP3/dheWYdI143Ik0K8Ck4o65U3axNatK8AxxYZSUiUAvF
wGrAZXkr/z9S9z+QpynpDsy9btQK0A2hhRnRxe8bVS21G5mTlxkvBlefFG0b1i15
ALEWICuaLJT3ZgsIr13C6Tfznjj3xkFy/wN0JDkWx3/EOLhN7r2orXAesEbukFyn
+BQ9qupqLgDCL7GnbwUZWFU4aYoJys+D4NawDPpc4cXKYHVf/c8OEdwCQggrDadE
q9fWnGzV/ERHJbS49Wftnsm7l9Wt1Nx5gIEKpeMcfWzXX/LdptUnEMJEHkcG15Z9
s3l2aNYbpHn5FezgQXG44C8+j6jErtwt3sid+padb9194uCURIGYMkhssqWsoznw
PN9Ebr3O95E2WFBUL2N7
=+/dq
-----END PGP SIGNATURE-----