xcb_xinerama_is_active(3)
π xcb_xinerama_is_active β the XCB Requests girlies π
okay so bestie, welcome to xcb_xinerama_is_active(3) β it's a lil request function from the xcb library that lives in <xcb/xinerama.h> and it's about finding out whether Xinerama is, like, active. that's the whole vibe. the NAME section is literally just the function name with nothing after it, which honestly? iconic minimalism. periodt.
β¨ SYNOPSIS β¨
first up, the include:
#include <xcb/xinerama.h>
π Request function
xcb_xinerama_is_active_cookie_t
xcb_xinerama_is_active(xcb_connection_t *conn,
yes bestie the signature just stops there in the original page π we don't make the rules, we just report them faithfully. no cap.
π¦ Reply datastructure
typedef struct xcb_xinerama_is_active_reply_t {
uint8_t response_type;
uint8_t pad0;
uint16_t sequence;
uint32_t length;
uint32_t state;
} xcb_xinerama_is_active_reply_t;
πΈ Reply function
xcb_xinerama_is_active_reply_t
*xcb_xinerama_is_active_reply(xcb_connection_t *conn,
xcb_xinerama_is_active_cookie_t cookie, xcb_generic_error_t **e);
π«Ά REQUEST ARGUMENTS π«Ά
connβ The XCB connection to X11. it's the lil thread that ties you to the server, your main character connection, yk?
π REPLY FIELDS π
response_typeβ the type of this reply, and in this case it'sXCB_XINERAMA_IS_ACTIVE. this field is also chillin' insidexcb_generic_reply_t, so you can use it to tell your replies apart from each other. very "which one of y'all is which" energy.sequenceβ the sequence number of the last request that got processed by the X11 server. it's giving tracking number for your request π§Ύlengthβ the length of the reply, measured in words. and a word here is 4 bytes, bestie, don't forget that part.stateβTODO: NOT YET DOCUMENTED.yeah. they left us on read. π
β DESCRIPTION β
...there's literally nothing here. the section exists and it's empty. the void. the silence. the audacity π lowkey obsessed with how much they didn't say.
π RETURN VALUE π
it returns an xcb_xinerama_is_active_cookie_t. and okay, listen β errors have to be handled when you call the reply function xcb_xinerama_is_active_reply. that's the deal.
but if you'd rather handle errors in the event loop instead, use xcb_xinerama_is_active_unchecked. and if you want the whole rundown on how that works, go read xcb-requests(3) β it's the lore drop you need fr fr.
π₯ ERRORS π₯
this request does never generate any errors. zero. none. not a single one. it's the chillest request in the whole building, no drama, no chaos, just vibes β¨
π SEE ALSO π
nothing listed. empty. a whole SEE ALSO section with nothing to see. we love a mysterious queen π
π AUTHOR π
Generated from xinerama.xml. and if you've got corrections or improvements, hit up xcb@lists.freedesktop.org β they wanna hear from you, bestie.
and that's the page!! π this lil manual page comes to you from X Version 11 and libxcb 1.17.0 β yeah, the whole thing is xcb_xinerama_is_active(3), top to bottom, and now you know it inside and out. slay, you're a Unix girlie now πβ¨π¦
π¦ 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