xcb_glx_gen_lists(3)

💅 xcb_glx_gen_lists — the XCB Requests page, bestie edition

okay so real talk, this is xcb_glx_gen_lists, one of those little GLX request pages from the XCB fam (that's the X protocol C binding, mwah). If you're poking at GLX from C and you found your way here, welcome, you're gonna do great. ✨

---

🌸 NAME

xcb_glx_gen_lists — bestie, the original page literally leaves this blank. No summary. Nothing. It's giving mysterious. 👀 (So, uh, no extra lore from me either — facts only, that's the rule.)

---

🎀 SYNOPSIS

Request function

#include <xcb/glx.h>

xcb_glx_gen_lists_cookie_t xcb_glx_gen_lists(xcb_connection_t *conn,
       xcb_glx_context_tag_t context_tag, int32_t range);

Reply datastructure

typedef struct xcb_glx_gen_lists_reply_t {
    uint8_t  response_type;
    uint8_t  pad0;
    uint16_t sequence;
    uint32_t length;
    uint32_t ret_val;
} xcb_glx_gen_lists_reply_t;

Reply function

xcb_glx_gen_lists_reply_t
       *xcb_glx_gen_lists_reply(xcb_connection_t *conn,
       xcb_glx_gen_lists_cookie_t cookie, xcb_generic_error_t **e);

so like, you fire off the request, you get a cookie back (adorable, iconic, no notes 🍪), and then you cash that cookie in with the reply function. That's the whole XCB vibe, iykyk.

---

💖 REQUEST ARGUMENTS

• conn — your XCB connection to X11. Your lil lifeline to the server, she's the main character here.
• context_tag — TODO: NOT YET DOCUMENTED. yeah babe, the docs said what they said, and I'm not out here making stuff up. 🙈
• range — also TODO: NOT YET DOCUMENTED. Same energy. We simply do not know from this page, and I refuse to guess. 💀

---

✨ REPLY FIELDS

• response_type — the type of this reply. In this case it's XCB_GLX_GEN_LISTS. This field also lives in the xcb_generic_reply_t, so you can use it to tell your replies apart from each other (very "which one of you is you" of it).
• sequence — the sequence number of the last request the X11 server processed. Her little receipt number 🧾.
• length — how long the reply is, in words. And a word is 4 bytes, so don't come at it with word-of-the-day energy, it's a unit of measurement bestie 📏.
• ret_val — TODO: NOT YET DOCUMENTED. yeah. Again. The mystery continues 👑.

---

🦋 DESCRIPTION

Nothing here. Genuinely. The section exists and there is nothing in it. It's giving silent treatment, it's giving "read the rest of the page and figure it out." No cap. 🌈

---

🫶 RETURN VALUE

You get back an xcb_glx_gen_lists_cookie_t. Cute! But heads up: errors have to be handled when you call the reply function xcb_glx_gen_lists_reply. You don't get to just vibe and ignore them, okay?

If you'd rather handle errors in the event loop instead, use xcb_glx_gen_lists_unchecked. See xcb-requests(3) for the details — that page has the whole breakdown, go read her. 💜

---

🔥 ERRORS

This request does never generate any errors.

fr fr. Zero. None. She's unproblematic. Slay. 💅

---

⭐ SEE ALSO

(empty — the original page lists nothing here, so there's nothing for me to pass along. Not me being lazy, I promise 😭)

---

👑 AUTHOR

Generated from glx.xml. Contact xcb@lists.freedesktop.org for corrections and improvements — so if something's off, email the homies, they fix, we all eat. 🍓

---

mwah, that's the page. go forth and request responsibly, bestie. 🧚

sign-off vibes: this one's from X Version 11, riding with libxcb 1.17.0, and yes, it's still called xcb_glx_gen_lists(3) around these parts. periodt. ✨