xcb_randr_set_monitor(3)
π xcb_randr_set_monitor β the XCB Requests era
okay bestie, welcome to xcb_randr_set_monitor(3) π this one lives in the XCB Requests family, and honestly? it's giving "short and mysterious." let's get into it π
β¨ NAME β¨
xcb_randr_set_monitor β no description, and we're just gonna sit with that π the manpage literally leaves this blank, so no cap, that's all the NAME section gives us.
πΈ SYNOPSIS πΈ
first thing's first, you gotta pull in the header, periodt:
#include <xcb/randr.h>
π¦ Request function π¦
and here's the actual function, character for character, don't you dare paraphrase it:
xcb_void_cookie_t xcb_randr_set_monitor(xcb_connection_t *conn,
xcb_window_t window, xcb_randr_monitor_info_t *monitorinfo);
π REQUEST ARGUMENTS π
connβ your XCB connection to X11. your lil hotline to the server, basically πwindowβ TODO: NOT YET DOCUMENTED. i know, i know π the docs really said "figure it out bestie."monitorinfoβ TODO: NOT YET DOCUMENTED. same energy, same silence π
ngl, two of the three arguments here are literally undocumented in the source. i'm not gonna make stuff up β that would be so not slay. all we know is what's written, and what's written is "TODO."
π DESCRIPTION π
there is no DESCRIPTION text. that's it. that's the whole vibe. the section exists, the words do not πβ¨
π RETURN VALUE π
this one hands you back an xcb_void_cookie_t. and because it's a void cookie, any errors (if there even are any) have to get handled in the event loop, okay? that's the whole deal π₯
but wait β if you'd rather handle errors directly with xcb_request_check instead, then you wanna use xcb_randr_set_monitor_checked π that's your girl for the direct-check route.
for all the deets on how that whole checked/unchecked thing works, go read xcb-requests(3). iykyk β
π ERRORS π
good news, icon behavior: this request does never generate any errors. zero. none. nothing. clean sheet, no drama, we love to see it π«Ά
π SEE ALSO π
the original page has nothing listed here. nothing! so there's nothing for me to send you to, bestie. go forth unguided π§
π AUTHOR π
generated from randr.xml π if you spot something wrong and wanna fix it or improve it, hmu at xcb@lists.freedesktop.org β they're the ones taking corrections and improvements π
and that's the whole page, fr fr. X Version 11, libxcb 1.17.0 β that's the version energy this beauty is running on, so when you cite it, cite it proud β¨ππΈ bye bestie, go set some monitors π
π¦ where this page comes from
- alpine 3.22: libxcb-doc 1.17.0-r0 Β· MIT
- alpine 3.23: libxcb-doc 1.17.0-r1 Β· MIT
- alpine 3.24: libxcb-doc 1.17.0-r2 Β· MIT
- arch rolling: libxcb 1.17.0-1 Β· X11
- centos-stream 10: libxcb-devel 1.17.0-3.el10 Β· X11
- debian trixie: libxcb-doc 1.17.0-2
- fedora 43: libxcb-devel 1.17.0-6.fc43 Β· X11
- fedora 43: libxcb-devel 1.17.0-6.fc43 Β· X11
- fedora 44: libxcb-devel 1.17.0-7.fc44 Β· X11
- fedora 44: libxcb-devel 1.17.0-7.fc44 Β· X11
- nixpkgs unstable: libxcb 1.17.0
- opensuse-leap 16.0: libxcb-devel-doc 1.17.0-160000.2.2 Β· MIT
- ubuntu questing: libxcb-doc 1.17.0-2build1
- ubuntu resolute: libxcb-doc 1.17.0-2ubuntu1
- ubuntu stonking: libxcb-doc 1.17.0-2ubuntu1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms