XCB_GLX_QUERY_EXTENSIONS_STRING_REPLY(3)
π xcb_glx_query_extensions_string β XCB Requests π
okay bestie, welcome to the group chat for xcb_glx_query_extensions_string(3) π
this one lives in the XCB Requests corner of the manual, and we're gonna get you fluent, no cap.
β¨ NAME β¨
xcb_glx_query_extensions_string β and that's it, that's the whole description, the original page literally leaves it blank so I'm not gonna invent lore for it π«Ά
πΈ SYNOPSIS πΈ
First thing, you gotta pull in the header:
#include <xcb/glx.h>
π Request function
xcb_glx_query_extensions_string_cookie_t
xcb_glx_query_extensions_string(xcb_connection_t *conn,
uint32_t screen);
π¦ Reply datastructure
typedef struct xcb_glx_query_extensions_string_reply_t {
uint8_t response_type;
uint8_t pad0;
uint16_t sequence;
uint32_t length;
uint8_t pad1[4];
uint32_t n;
uint8_t pad2[16];
} xcb_glx_query_extensions_string_reply_t;
π§ Reply function
xcb_glx_query_extensions_string_reply_t
*xcb_glx_query_extensions_string_reply(xcb_connection_t *conn,
xcb_glx_query_extensions_string_cookie_t cookie,
xcb_generic_error_t **e);
π REQUEST ARGUMENTS π
connβ your XCB connection to X11, the whole link to the server, the main character fr.screenβTODO: NOT YET DOCUMENTED.yeah bestie, the docs really said "figure it out" π it's auint32_t, that's what we know.
β REPLY FIELDS β
response_typeβ the type of this reply, and in this case it'sXCB_GLX_QUERY_EXTENSIONS_STRING. plot twist: this field also lives inxcb_generic_reply_t, so you can use it to tell replies apart from each other. iconic behavior tbh.sequenceβ the sequence number of the last request processed by the X11 server. it's giving receipts πlengthβ the length of the reply, in words (and a word is 4 bytes, don't forget, that's the whole trick).nβTODO: NOT YET DOCUMENTED.another mystery, we stay humble π
π DESCRIPTION π
...so the original page has literally nothing here. no cap. empty. blank. the vibe is immaculate but the content is not present π we move on.
π₯ RETURN VALUE π₯
Returns an xcb_glx_query_extensions_string_cookie_t. Errors have to be handled when calling the reply function xcb_glx_query_extensions_string_reply.
If you want to handle errors in the event loop instead, usexcb_glx_query_extensions_string_unchecked. Seexcb-requests(3)for details. yes bestie, that's a whole other manpage, go read it π«Ά
π ERRORS π
This request does never generate any errors. periodt. zero. none. slay. β¨
πΈ SEE ALSO πΈ
(empty, the original page gives us nothing here either, we simply vibe π¦)
π AUTHOR π
Generated from glx.xml. Contact xcb@lists.freedesktop.org for corrections and improvements. they're nice, they take feedback, go say hi if you find a typo π
and that's the whole page bestie!! π mwah π
this came from X Version 11, libxcb 1.17.0, and the page title situation is xcb_glx_query_extensions_string(3) β go forth and query those extension strings, you absolute legend ππ¦β¨
π¦ 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