xcb_glx_is_list(3)

💅 xcb_glx_is_list — the XCB Requests glow-up ✨

okay so bestie, we're in xcb_glx_is_list(3) territory, from the XCB Requests corner of the universe, and I'm gonna walk you through it like we're texting at 2am 🫶

---

🌸 NAME 🌸

xcb_glx_is_list — and that's it, that's the whole name section. The original left the description blank, so no cap, there is literally nothing else here. Moving on, periodt 💀

---

✨ SYNOPSIS ✨

First things first, you gotta pull in the header:

#include <xcb/glx.h>

🎀 Request function 🎀

xcb_glx_is_list_cookie_t xcb_glx_is_list(xcb_connection_t *conn,
       xcb_glx_context_tag_t context_tag, uint32_t list);

🦋 Reply datastructure 🦋

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

🧚 Reply function 🧚

xcb_glx_is_list_reply_t *xcb_glx_is_list_reply(xcb_connection_t *conn,
       xcb_glx_is_list_cookie_t cookie, xcb_generic_error_t **e);

---

💖 REQUEST ARGUMENTS 💖

• conn — your XCB connection to X11, the whole reason we're here, the main character honestly 👑
• context_tag — TODO: NOT YET DOCUMENTED. yeah babe, the docs just didn't show up to class that day 😭
• list — TODO: NOT YET DOCUMENTED. same energy, same mystery, we simply do not know 🙈

---

🌈 REPLY FIELDS 🌈

• response_type — the type of this reply, which in this case is XCB_GLX_IS_LIST. This field is also hanging out in the xcb_generic_reply_t, so you can use it to tell your replies apart from each other. it's giving "name tag at a party" 🎀
• sequence — the sequence number of the last request the X11 server actually processed 🔥
• length — how long the reply is, measured in words. and bestie, a word is 4 bytes, don't forget it 💅
• ret_val — TODO: NOT YET DOCUMENTED. once again the docs ghosted us 💀

---

⭐ DESCRIPTION ⭐

<crickets> …yeah. The original page left this section empty, so there is genuinely nothing here to describe. Not me writing a whole section about a section that has no content 😭

---

💜 RETURN VALUE 💜

It hands you back an xcb_glx_is_list_cookie_t. Errors? Those have to be handled when you call the reply function xcb_glx_is_list_reply.

But if you'd rather handle errors in the event loop instead, use xcb_glx_is_list_unchecked. See xcb-requests(3) for the deets, iykyk ✨

---

🍓 ERRORS 🍓

This request does never generate any errors. not a single one. flawless behaviour, we love to see it 🌸

---

🫶 SEE ALSO 🫶

Also empty in the original, bestie. No cross-references, no friends, just vibes 🦋

---

👑 AUTHOR 👑

Generated from glx.xml. Contact xcb@lists.freedesktop.org for corrections and improvements. like, respectfully, slide into their inbox if something's wrong 📩

---

a lil warning from me to you: those TODO: NOT YET DOCUMENTED. fields are exactly that — undocumented. I'm not gonna make stuff up about them, and neither should you. 💅

---

okay that's the whole page, you ate it, you understood it, you're iconic 🌟 this was X Version 11, libxcb 1.17.0, and the page is xcb_glx_is_list(3). mwah, go forth and slay 💖✨🎀