xcb_glx_flush(3)

💅 NAME

xcb_glx_flush — bestie the name section is literally empty 😭 the original manpage leaves it blank, so we're not gonna invent a description that isn't there. It's a GLX flush request, that's the vibe, that's all the page gives us. iykyk 🦋

---

✨ SYNOPSIS

okay so first you gotta pull in the header, she's required:

#include <xcb/glx.h>

🎀 Request function

here's the whole girl, one function, two args, no drama:

xcb_void_cookie_t xcb_glx_flush(xcb_connection_t *conn,
       xcb_glx_context_tag_t context_tag);

---

🌸 REQUEST ARGUMENTS

• conn — the XCB connection to X11. she's your lil hotline to the server, keep her close 🫶
• context_tag — TODO: NOT YET DOCUMENTED. yeah bestie, that's the literal text in the manpage. nobody wrote it up yet 🙈 we are NOT making something up, that's the whole truth.

---

💀 DESCRIPTION

the DESCRIPTION section is empty. like, actually empty. there is nothing here. no prose, no notes, no lore. the original just has the heading and then straight-up nothing. iconic in a cursed way honestly 💀✨

---

⭐ RETURN VALUE

she hands you back an xcb_void_cookie_t. 🎀

any errors (if there even are any) have to be handled over in the event loop, that's the move.

but listen — if you'd rather deal with errors directly with xcb_request_check, then you use xcb_glx_flush_checked instead, periodt. see xcb-requests(3) for the details 👑

---

🌈 ERRORS

this request never generates any errors. not a single one. zero. clean sheet. slay 💅

---

🦋 SEE ALSO

nothing listed, bestie. the SEE ALSO section is empty in the original — no cross-references, no nothing. (the xcb-requests(3) mention lives up in RETURN VALUE, not here, so don't get it twisted 🫶)

---

👑 AUTHOR

Generated from glx.xml. Contact xcb@lists.freedesktop.org for corrections and improvements. 💌

---

and that's the whole page, bestie!! this one came from X Version 11, libxcb 1.17.0, and the manual name is xcb_glx_flush in section 3 — go forth and flush responsibly, mwah 💖✨🌸