xcb_list_extensions(3)

✨ xcb_list_extensions — bestie, let's go get the tea on every extension ✨

okay so real talk, this is a manual page for xcb_list_extensions from the XCB Requests corner of the X universe 💖 it lives in the xcb_list_extensions(3) manual, and it's your little backstage pass to asking the X11 server "hey girl, what extensions you got??" 🎀

---

🌸 NAME 🌸

xcb_list_extensions — (yeah bestie, the original literally leaves the description blank here, iconic of it, so we're not making one up 💅)

---

✨ SYNOPSIS ✨

First things first, you gotta let it in:

#include <xcb/xproto.h>

💌 Request function

xcb_list_extensions_cookie_t xcb_list_extensions(xcb_connection_t *conn,

🦋 Reply datastructure

typedef struct xcb_list_extensions_reply_t {
    uint8_t  response_type;
    uint8_t  names_len;
    uint16_t sequence;
    uint32_t length;
    uint8_t  pad0[24];
} xcb_list_extensions_reply_t;

💖 Reply function

xcb_list_extensions_reply_t
       *xcb_list_extensions_reply(xcb_connection_t *conn,
       xcb_list_extensions_cookie_t cookie, xcb_generic_error_t **e);

🌈 Reply accessors

int xcb_list_extensions_names_length(const xcb_list_extensions_reply_t
       *reply);

xcb_str_iterator_t xcb_list_extensions_names_iterator(const
       xcb_list_extensions_reply_t *reply);

---

🫶 REQUEST ARGUMENTS 🫶

• conn — the XCB connection to X11. your lil hotline to the server, she's the one you're asking 💅

---

👑 REPLY FIELDS 👑

• response_type — the type of this reply, and in this case it's XCB_LIST_EXTENSIONS. this field also shows up in the xcb_generic_reply_t, so you can use it to tell replies apart from each other when they're all up in your queue 🎀
• sequence — the sequence number of the last request processed by the X11 server. lowkey your receipt number, keep it in mind 📝
• length — the length of the reply, in words (and a word is 4 bytes, no cap) ✨
• names_len — TODO: NOT YET DOCUMENTED. yeah bestie the docs literally say that, not me, I'm just the messenger 😭

---

💀 DESCRIPTION 💀

the original page is literally empty here. not a single word. it's giving mystery, it's giving main character energy, it's giving absolutely no information 🙈 so I'm not gonna invent any, because the vibes matter but the facts matter more, periodt.

---

💜 RETURN VALUE 💜

Returns an xcb_list_extensions_cookie_t. and listen, errors have to be handled when you call the reply function xcb_list_extensions_reply. that's the deal, bestie 🫶

If you'd rather handle errors in the event loop instead, use xcb_list_extensions_unchecked. see xcb-requests(3) for the details on that whole situation 📚

---

🔥 ERRORS 🔥

This request does never generate any errors. not one. zero. she's unproblematic like that ✨

---

🌸 SEE ALSO 🌸

(bestie, the original leaves this section empty too — nothing listed, nothing linked, no crumbs 🍓)

---

🌈 AUTHOR 🌈

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

---

heads up babes: names_len is still TODO: NOT YET DOCUMENTED. in the original, and the DESCRIPTION and SEE ALSO sections are genuinely blank there too. I kept them exactly as empty as they came — no invented lore, no fake facts 💅

and that's a wrap on this one, bestie 💖 this page came from libxcb 1.17.0, part of X Version 11, and it's the xcb_list_extensions(3) manual — go forth and ask the server what she's working with 🎀✨🦋