XCB_INPUT_GET_EXTENSION_VERSION_UNCHECKED(3)
π NAME π
xcb_input_get_extension_version β bestie, this is the X Input extension version asker, and honestly? The docs left it blank for us. We ball anyway. π
β¨ SYNOPSIS β¨
Header first, always:
#include <xcb/xinput.h>
π¦ Request function
xcb_input_get_extension_version_cookie_t
xcb_input_get_extension_version(xcb_connection_t *conn,
uint16_t name_len, const char *name);
π«Ά Reply datastructure
typedef struct xcb_input_get_extension_version_reply_t {
uint8_t response_type;
uint8_t xi_reply_type;
uint16_t sequence;
uint32_t length;
uint16_t server_major;
uint16_t server_minor;
uint8_t present;
uint8_t pad0[19];
} xcb_input_get_extension_version_reply_t;
πΈ Reply function
xcb_input_get_extension_version_reply_t
*xcb_input_get_extension_version_reply(xcb_connection_t *conn,
xcb_input_get_extension_version_cookie_t cookie,
xcb_generic_error_t **e);
π REQUEST ARGUMENTS
connβ the XCB connection to X11. Your little phone line to the server, no cap. πname_lenβ TODO: NOT YET DOCUMENTED. Yeah bestie, they really just left us on read for this one. πnameβ TODO: NOT YET DOCUMENTED. Same energy. The mystery stays mysterious. π΅οΈβοΈ
π REPLY FIELDS
response_typeβ the type of this reply, and in this case it'sXCB_INPUT_GET_EXTENSION_VERSION. This field also lives in thexcb_generic_reply_t, so you can use it to tell your replies apart from each other like, "wait, which one are you?" and it just tells you. Iconic behaviour, honestly. β¨sequenceβ the sequence number of the last request the X11 server actually processed. Basically the server's "seen it, handled it π " receipt.lengthβ how long the reply is, measured in words. And a word here is4bytes, just so we're clear. π§xi_reply_typeβ TODO: NOT YET DOCUMENTED. Ugh.server_majorβ TODO: NOT YET DOCUMENTED. The lore is missing, bestie.server_minorβ TODO: NOT YET DOCUMENTED. Also missing.presentβ TODO: NOT YET DOCUMENTED. Genuinely nothing. Not a crumb. π
π DESCRIPTION
(The original page has literally nothing here. A blank canvas. Main character silence. I'm not gonna invent facts to fill it, because that's not the vibe β the vibe is accuracy.)
π₯ RETURN VALUE
You get back an xcb_input_get_extension_version_cookie_t. πͺ A cookie! And cookies mean the errors don't show up here β you have to handle them when you call the reply function, xcb_input_get_extension_version_reply.
If you'd rather handle your errors in the event loop instead, then use xcb_input_get_extension_version_unchecked. And for the whole lore on how this cookie/reply dance works, go read xcb-requests(3). Periodt. π
π ERRORS
This request does never generate any errors. Not one. Zero. Clean sheet, flawless, no drama. Slay. β¨
π SEE ALSO
(Nothing listed on this page β go touch some other manpages, bestie.)
π AUTHOR
Generated from xinput.xml. If you've got corrections or improvements, hit up xcb@lists.freedesktop.org β they're literally asking, so don't be shy. π¬
And that's the whole page, bestie! This was xcb_input_get_extension_version(3) from the XCB Requests manual, coming to you courtesy of X Version 11, libxcb 1.17.0. Stay hydrated, stay linked, and remember: read the reply, handle the cookie. π
π¦
π¦ 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