XCB_GLX_VENDOR_PRIVATE_WITH_REPLY_UNCHECKED(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_vendor_private_with_reply β€” bestie, it's a libxcb request page

okay so. this is a page from the XCB Requests manual β€” like, the X protocol crew's whole thing β€” and today's main character is xcb_glx_vendor_private_with_reply. yes the name is a mouthful, no we are not shortening it, it's ✨iconic✨ exactly as it is.


🌸 NAME 🌸

xcb_glx_vendor_private_with_reply β€” and that's literally all the original says about it, so that's all we're claiming. no cap. πŸ™ˆ


✨ SYNOPSIS ✨

first up, you gotta bring in the header, obvi:

#include <xcb/glx.h>

πŸŽ€ Request function

xcb_glx_vendor_private_with_reply_cookie_t
       xcb_glx_vendor_private_with_reply(xcb_connection_t *conn,
       uint32_t vendor_code, xcb_glx_context_tag_t context_tag,
       uint32_t data_len, const uint8_t *data);

πŸ¦‹ Reply datastructure

typedef struct xcb_glx_vendor_private_with_reply_reply_t {
    uint8_t  response_type;
    uint8_t  pad0;
    uint16_t sequence;
    uint32_t length;
    uint32_t retval;
    uint8_t  data1[24];
} xcb_glx_vendor_private_with_reply_reply_t;

πŸ’– Reply function

xcb_glx_vendor_private_with_reply_reply_t
       *xcb_glx_vendor_private_with_reply_reply(xcb_connection_t *conn,
       xcb_glx_vendor_private_with_reply_cookie_t cookie,
       xcb_generic_error_t **e);

🌈 Reply accessors

uint8_t *xcb_glx_vendor_private_with_reply_data_2(const
       xcb_glx_vendor_private_with_reply_request_t *reply);
int xcb_glx_vendor_private_with_reply_data_2_length(const
       xcb_glx_vendor_private_with_reply_reply_t *reply);
xcb_generic_iterator_t
       xcb_glx_vendor_private_with_reply_data_2_end(const
       xcb_glx_vendor_private_with_reply_reply_t *reply);

🌟 REQUEST ARGUMENTS 🌟

  • conn β€” the XCB connection to X11. your link to the server, your ride or die 🫢
  • vendor_code β€” TODO: NOT YET DOCUMENTED. yeah babe the docs really just left us on read here 😭
  • context_tag β€” TODO: NOT YET DOCUMENTED. same vibe, nobody wrote it down πŸ’€
  • data_len β€” TODO: NOT YET DOCUMENTED. mystery behavior, we stay humble πŸ™ˆ
  • data β€” TODO: NOT YET DOCUMENTED. also undocumented, also not our fault ✨

πŸ‘‘ REPLY FIELDS πŸ‘‘

  • response_type β€” the type of this reply, and in this case it's XCB_GLX_VENDOR_PRIVATE_WITH_REPLY. this field also lives in the xcb_generic_reply_t, which is how you tell replies apart from each other β€” it's giving name tag at a party πŸŽ€
  • sequence β€” the sequence number of the last request the X11 server processed. the receipts, basically 🧾
  • length β€” the length of the reply, measured in words, and a word is 4 bytes. so, math, but make it X11 ✨
  • retval β€” TODO: NOT YET DOCUMENTED. 🫠
  • data1 β€” TODO: NOT YET DOCUMENTED. 🫠

πŸ’œ DESCRIPTION πŸ’œ

okay so the original page has literally nothing under DESCRIPTION. it's a blank canvas. an empty group chat. no notes, no lore, no tea. we are not inventing any β€” that's the rule, bestie. πŸ’…


πŸ”₯ RETURN VALUE πŸ”₯

it hands you back an xcb_glx_vendor_private_with_reply_cookie_t. a cookie!! πŸͺ

errors? you handle those when you call the reply function, xcb_glx_vendor_private_with_reply_reply.

and if you'd rather handle errors in the event loop instead, use xcb_glx_vendor_private_with_reply_unchecked. see xcb-requests(3) for the details β€” go read it, it's the blueprint fr fr.


πŸ’€ ERRORS πŸ’€

This request does never generate any errors. not a single one. zero drama, no chaos, immaculate behavior. slay. ✨

🌈 SEE ALSO 🌈

yeah the original leaves this empty too. nothing linked, nothing referenced. we're keeping it exactly that way β€” an empty shelf with great energy. πŸ¦‹


πŸŽ€ AUTHOR πŸŽ€

generated from glx.xml. contact xcb@lists.freedesktop.org for corrections and improvements β€” they're literally asking for your notes, so if something's off, tell them, don't just suffer in silence bestie 🫢


and that's the whole page, mwah πŸ’–. this one came from the X Version 11 manual set, libxcb 1.17.0, and it's a xcb_glx_vendor_private_with_reply(3) situation through and through. stay hydrated, go read xcb-requests(3), and remember: undocumented fields are still fields. periodt. πŸ’…βœ¨