xcb_res_query_version(3)
β¨ xcb_res_query_version β¨
okay bestie, so this is a lil XCB request from the res extension family β it's called xcb_res_query_version and it lives in the libxcb world, page 3 of the manual. it's giving "hi, what version are we on" energy, and honestly? iconic. π
πΈ SYNOPSIS πΈ
first things first, you gotta pull in the header:
#include <xcb/res.h>
π Request function
xcb_res_query_version_cookie_t
xcb_res_query_version(xcb_connection_t *conn,
uint8_t client_major, uint8_t client_minor);
π¦ Reply datastructure
typedef struct xcb_res_query_version_reply_t {
uint8_t response_type;
uint8_t pad0;
uint16_t sequence;
uint32_t length;
uint16_t server_major;
uint16_t server_minor;
} xcb_res_query_version_reply_t;
π§ Reply function
xcb_res_query_version_reply_t
*xcb_res_query_version_reply(xcb_connection_t *conn,
xcb_res_query_version_cookie_t cookie, xcb_generic_error_t **e);
π REQUEST ARGUMENTS π
connβ the XCB connection to X11. she's the whole group chat, fr.client_majorβ TODO: NOT YET DOCUMENTED. yeah bestie, even the docs are being mysterious. πclient_minorβ TODO: NOT YET DOCUMENTED. same vibe, same mystery. π
π REPLY FIELDS π
response_typeβ the type of this reply, and in this specific case it'sXCB_RES_QUERY_VERSION. this field also shows up in thexcb_generic_reply_t, so you can use it to tell replies apart from each other. so useful, so slay. πsequenceβ the sequence number of the last request processed by the X11 server. she's keeping receipts. πlengthβ the length of the reply, in words (and a word here is 4 bytes, no cap). πserver_majorβ TODO: NOT YET DOCUMENTED. the mystery continues π«Άserver_minorβ TODO: NOT YET DOCUMENTED. mystery level: unlocked π₯
β¨ DESCRIPTION β¨
β¦so there's literally nothing here. like, the DESCRIPTION section is just vibes and empty space. no notes. moving on. π
π«Ά RETURN VALUE π«Ά
she returns an xcb_res_query_version_cookie_t. and listen β errors have to be handled when you call the reply function, xcb_res_query_version_reply. that's the moment of truth, bestie.
if you'd rather handle errors in the event loop instead, use xcb_res_query_version_unchecked. see xcb-requests(3) for the deets. iykyk. π
π ERRORS π
this request does never generate any errors. not one. zero. she's unproblematic like that. β¨
π₯ SEE ALSO π₯
β¦nothing listed. it's giving empty. it's giving "the see also section went to get milk". π
π AUTHOR π
generated from res.xml. contact xcb@lists.freedesktop.org for corrections and improvements β they're the ones to slide into, fr fr. π
and that's the whole page, bestie π big kisses to X Version 11 and to libxcb 1.17.0 for making this lil xcb_res_query_version(3) moment possible. go query your versions, queen. πβ¨π¦
π¦ 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