XCB_GLX_QUERY_EXTENSIONS_STRING_REPLY(3)

πŸ“¦
version 1.17.0 Β· 4 versions
, in alpine 3.22, alpine 3.23, alpine 3.24, arch rolling, centos-stream 10, debian trixie, fedora 43, fedora 44, nixpkgs unstable, opensuse-leap 16.0, ubuntu questing, ubuntu resolute, ubuntu stonking

πŸ’– 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 a uint32_t, that's what we know.

⭐ REPLY FIELDS ⭐

  • response_type β€” the type of this reply, and in this case it's XCB_GLX_QUERY_EXTENSIONS_STRING. plot twist: this field also lives in xcb_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, use xcb_glx_query_extensions_string_unchecked. See xcb-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 πŸŽ€πŸ¦‹βœ¨