xcb_glx_copy_context(3)

✨ xcb_glx_copy_context ✨

okay so bestie, we're diving into a page from the XCB Requests corner of the Unix manual — it's xcb_glx_copy_context(3) and honestly? it's giving mysterious. 🦋 the name itself is basically just xcb_glx_copy_context - with literally nothing after the dash, so buckle up, we're reading the vibes AND the facts. 💅

---

🌸 NAME 🌸

xcb_glx_copy_context — and that's it. no little tagline, no "does the thing with the contexts," nothing. the manpage left it blank. iconic behaviour, honestly. 😭

---

🎀 SYNOPSIS 🎀

first, the include. you gotta bring in the GLX header, no skips:

#include <xcb/glx.h>

✨ Request function ✨

and here's the actual function signature, character for character, no cap:

xcb_void_cookie_t xcb_glx_copy_context(xcb_connection_t *conn,
       xcb_glx_context_t src, xcb_glx_context_t dest, uint32_t mask,
       xcb_glx_context_tag_t src_context_tag);

---

🫶 REQUEST ARGUMENTS 🫶

every single one, in order, with their real types — here's the rundown:

• conn — your xcb_connection_t *, aka the XCB connection to X11. this one's the only arg the page actually explains, and it explains it as "The XCB connection to X11." periodt.
• src — an xcb_glx_context_t. the page says, and I quote: TODO: NOT YET DOCUMENTED. 💀
• dest — also an xcb_glx_context_t. and also: TODO: NOT YET DOCUMENTED.
• mask — a uint32_t. you guessed it: TODO: NOT YET DOCUMENTED. 🙈
• src_context_tag — an xcb_glx_context_tag_t. and once more, for the people in the back: TODO: NOT YET DOCUMENTED.

not me pointing out that four out of five arguments are literally undocumented in the source material. I'm not gonna make up what they do — that would be lying to you, and lying is NOT the vibe. if the manpage doesn't say it, I don't say it. 🫡

---

💜 DESCRIPTION 💜

okay so here's the tea: the DESCRIPTION section in the original is... empty. nothing. a void. a little blank space where the lore should be. 🌈

---

⭐ RETURN VALUE ⭐

this one's got actual content, slay. it returns an xcb_void_cookie_t. and here's the important part — errors (if any) have to be handled in the event loop. 🔥

if you'd rather handle errors directly with xcb_request_check instead, use xcb_glx_copy_context_checked. the details live in xcb-requests(3), so go read that one too, bestie. 📖

---

👑 ERRORS 👑

good news, genuinely: this request does never generate any errors. that's the whole section. clean. pristine. no drama. ✨

---

🧚 SEE ALSO 🧚

...it's empty. the section exists, the heading is there, and underneath it there is nothing. not a single reference. I'm keeping it exactly as empty as I found it because that's the rule. 💖

---

🍓 AUTHOR 🍓

generated from glx.xml. and if you've got corrections or improvements, hit up xcb@lists.freedesktop.org — they explicitly want the feedback. 🫶

---

and that's the whole page, babe! this one came from X Version 11, libxcb 1.17.0 — go forth and copy those contexts (whatever that means, since the manpage won't tell us 😭). mwah, stay hydrated, and may all your cookies be void. 💅🌈💜