xcb_test_get_version(3)

💅 xcb_test_get_version — bestie edition 💅

okay so you're here for xcb_test_get_version, which lives in the XCB Requests corner of the xcb_test_get_version(3) manual page. yes it's a mouthful. no we're not renaming it. it's iconic actually. ✨

---

🌸 NAME 🌸

xcb_test_get_version — (the original page literally leaves this blank, so we're just vibing with the name, no cap)

---

🦋 SYNOPSIS 🦋

#include <xcb/xtest.h>

✨ Request function ✨

xcb_test_get_version_cookie_t
       xcb_test_get_version(xcb_connection_t *conn,
       uint8_t major_version, uint16_t minor_version);

🎀 Reply datastructure 🎀

typedef struct xcb_test_get_version_reply_t {
    uint8_t  response_type;
    uint8_t  major_version;
    uint16_t sequence;
    uint32_t length;
    uint16_t minor_version;
} xcb_test_get_version_reply_t;

💖 Reply function 💖

xcb_test_get_version_reply_t
       *xcb_test_get_version_reply(xcb_connection_t *conn,
       xcb_test_get_version_cookie_t cookie, xcb_generic_error_t **e);

---

🌈 REQUEST ARGUMENTS 🌈

• conn — the XCB connection to X11. your whole lil pipeline to the server, she's the main character 🫶
• major_version — TODO: NOT YET DOCUMENTED. 😭 (not me, not my fault, that's literally what the page says)
• minor_version — TODO: NOT YET DOCUMENTED. 💀 (same energy, bestie)

---

⭐ REPLY FIELDS ⭐

• response_type — the type of this reply. in this case it's XCB_TEST_GET_VERSION. this field is also present in the xcb_generic_reply_t and you can use it to tell replies apart from each other. it's giving "name tag at a party" 🎀
• sequence — the sequence number of the last request processed by the X11 server. her lil receipt number fr fr
• length — the length of the reply, in words (and a word is 4 bytes, okurrr)
• major_version — TODO: NOT YET DOCUMENTED. 🙈
• minor_version — TODO: NOT YET DOCUMENTED. 🙈

---

🧚 DESCRIPTION 🧚

the DESCRIPTION section is empty. like, fully empty. the void. the silence. we love a mysterious queen 💅

---

🔥 RETURN VALUE 🔥

Returns an xcb_test_get_version_cookie_t. bestie, that's a cookie, not the actual answer — you gotta redeem it.

Errors have to be handled when calling the reply function xcb_test_get_version_reply.

If you want to handle errors in the event loop instead, use xcb_test_get_version_unchecked. See xcb-requests(3) for details. yes, we love an alternate route ✨

---

👑 ERRORS 👑

This request does never generate any errors. clean. pristine. no drama. we stan a low-maintenance request. 🌸

---

🍓 SEE ALSO 🍓

(okay the SEE ALSO section on this page is empty too — nothing listed. so the see-also vibe check is just… vibes. 🦋)

---

💜 AUTHOR 💜

Generated from xtest.xml. Contact xcb@lists.freedesktop.org for corrections and improvements.

---

and that's the whole page, bestie!! this came out of X Version 11 and libxcb 1.17.0, so if you're citing it anywhere cute, that's the source and version to quote. mwah 💋✨