xcb_record_query_version(3)
π xcb_record_query_version β the vibe check for Record extension versions π
okay bestie, welcome to the xcb_record_query_version page from the XCB Requests manual (yes, that's the manual name, we're keeping it, it's iconic). this is your girl explaining how you ask the X11 server "hey, what version of the Record extension are you running, bestie?" π¦
β¨ NAME β¨
xcb_record_query_version β soβ¦ the description here is literally blank in the original, no cap. π we move on.
πΈ SYNOPSIS πΈ
first things first, you gotta pull in the header:
#include <xcb/record.h>
π Request function
xcb_record_query_version_cookie_t
xcb_record_query_version(xcb_connection_t *conn,
uint16_t major_version, uint16_t minor_version);
π Reply datastructure
typedef struct xcb_record_query_version_reply_t {
uint8_t response_type;
uint8_t pad0;
uint16_t sequence;
uint32_t length;
uint16_t major_version;
uint16_t minor_version;
} xcb_record_query_version_reply_t;
π«Ά Reply function
xcb_record_query_version_reply_t
*xcb_record_query_version_reply(xcb_connection_t *conn,
xcb_record_query_version_cookie_t cookie,
xcb_generic_error_t **e);
β REQUEST ARGUMENTS β
connβ your XCB connection to X11, the group chat you're sending this into π±major_versionβ TODO: NOT YET DOCUMENTED. yeah she's a mystery, we don't know her πminor_versionβ TODO: NOT YET DOCUMENTED. same energy, no lore available π
π REPLY FIELDS π
response_typeβ the type of this reply, which in this case isXCB_RECORD_QUERY_VERSION. this field also lives inxcb_generic_reply_t, so you can use it to tell your replies apart from each other πsequenceβ the sequence number of the last request processed by the X11 server, like a lil timestamp for the gossip π«lengthβ the length of the reply, in words. and bestie, a word here is 4 bytes, remember that πmajor_versionβ TODO: NOT YET DOCUMENTED. still a mystery π΅οΈminor_versionβ TODO: NOT YET DOCUMENTED. also a mystery, we know nothing, zero tea π
π¦ DESCRIPTION π¦
literally nothing here in the original. the section exists, it's just empty. slay, i guess β¨
π RETURN VALUE π
it hands you back an xcb_record_query_version_cookie_t πͺ β and here's the thing, bestie: errors have to be handled when you call the reply function xcb_record_query_version_reply.
if you'd rather handle errors in the event loop instead, use xcb_record_query_version_unchecked. see xcb-requests(3) for details, fr fr π
π₯ ERRORS π₯
this request does never generate any errors. not one. clean run, no drama, we love that for her π
π§ SEE ALSO π§
empty in the original too. no cross-refs, no links, just vibes πΈ
π AUTHOR π
Generated from record.xml. Contact xcb@lists.freedesktop.org for corrections and improvements. π«Ά
and that's the whole page, bestie! this one came from libxcb 1.17.0, part of X Version 11, and yeah, the page title is xcb_record_query_version(3) in case you forgot already π
periodt, go forth and query those versions β¨ππ
π¦ 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