xcb_glx_vendor_private(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 ✨

okay bestie, welcome to the manual page for xcb_glx_vendor_private(3) 💅 it lives in the XCB Requests section of the manual, and honestly? it's giving "mystery box" energy, because most of it is literally a TODO. no cap. let's get into it 🫶

🌸 NAME 🌸

xcb_glx_vendor_private — and that's it, that's the whole name 😭 the description field is empty in the source, so we're all just out here vibing with the function name and nothing else. iconic, honestly.

🎀 SYNOPSIS 🎀

First things first, you gotta include the header, periodt:

#include <xcb/glx.h>

✨ Request function ✨

xcb_void_cookie_t xcb_glx_vendor_private(xcb_connection_t *conn,
       uint32_t vendor_code, xcb_glx_context_tag_t context_tag,
       uint32_t data_len, const uint8_t *data);

that's the whole signature, copy it exactly, don't be out here freestyling the types 👑 the return type is xcb_void_cookie_t, which is giving "I'm a cookie but I'm not gonna hand you any data" 🍓

💖 REQUEST ARGUMENTS 💖

every single arg, bestie, no skipping:

  • conn — the XCB connection to X11. the link between you and the X server, your whole situationship 🌈
  • vendor_code — TODO: NOT YET DOCUMENTED. 🫠
  • context_tag — TODO: NOT YET DOCUMENTED. 🫠
  • data_len — TODO: NOT YET DOCUMENTED. 🫠
  • data — TODO: NOT YET DOCUMENTED. 🫠

like... the docs really said "figure it out yourself, queen" and left 💀 no shade, that's just what the source says, and I'm not about to invent lore that isn't there. we respect the canon.

🦋 DESCRIPTION 🦋

...

yeah. it's blank. the description section is empty, bestie 😭 not a single sentence. the whole page is basically a placeholder with a banger function signature attached. we move.

👑 RETURN VALUE 👑

it returns an xcb_void_cookie_t. and here's the tea: any errors (if there even are any) have to be handled over in the event loop, not right here. that's just how void cookies roll ✨

if you'd rather handle errors directly with xcb_request_check instead, then use xcb_glx_vendor_private_checked — that's the checked twin, the one who actually tells you what went wrong 🫶

peep xcb-requests(3) for all the deets on how that works, iykyk.

🔥 ERRORS 🔥

This request does never generate any errors.

not one. zero. zilch. the request is on its best behaviour, always 💅 a well-behaved king.

🌈 SEE ALSO 🌈

  • (nothing listed) 🦗🦗🦗 the crickets are cricket-ing, bestie. the SEE ALSO section is empty in the source.

💜 AUTHOR 💜

Generated from glx.xml. if you spot something wrong and wanna fix it or improve it, hit up xcb@lists.freedesktop.org 📧 they're the ones who can make corrections and improvements happen. community slay.

and that's the whole page, babe 🎀 this beauty comes to you from X Version 11, shipping with libxcb 1.17.0 — mwah, take care of her 💖✨🦋

📦 where this page comes from