xcb_randr_lis...er_properties(3)

💖 xcb_randr_list_provider_properties 💖

okay bestie so this is a page from the XCB Requests section of the manual — it's xcb_randr_list_provider_properties(3), and yes the title in the header gets truncated like that, we don't make the rules 💅

It's the request that asks your X server for a list of the properties on a RandR provider. That's it. That's the whole vibe. Let's go ✨

---

🌸 NAME 🌸

xcb_randr_list_provider_properties — no description given, the original literally just trails off, so we're all finding out together 🙈

---

🦋 SYNOPSIS 🦋

#include <xcb/randr.h>

✨ Request function

xcb_randr_list_provider_properties_cookie_t
       xcb_randr_list_provider_properties(xcb_connection_t *conn,
       xcb_randr_provider_t provider);

✨ Reply datastructure

typedef struct xcb_randr_list_provider_properties_reply_t {
    uint8_t  response_type;
    uint8_t  pad0;
    uint16_t sequence;
    uint32_t length;
    uint16_t num_atoms;
    uint8_t  pad1[22];
} xcb_randr_list_provider_properties_reply_t;

✨ Reply function

xcb_randr_list_provider_properties_reply_t
       *xcb_randr_list_provider_properties_reply(xcb_connection_t *conn,
       xcb_randr_list_provider_properties_cookie_t cookie,
       xcb_generic_error_t **e);

✨ Reply accessors

xcb_atom_t *xcb_randr_list_provider_properties_atoms(const
       xcb_randr_list_provider_properties_request_t *reply);

int xcb_randr_list_provider_properties_atoms_length(const
       xcb_randr_list_provider_properties_reply_t *reply);

xcb_generic_iterator_t
       xcb_randr_list_provider_properties_atoms_end(const
       xcb_randr_list_provider_properties_reply_t *reply);

---

🎀 REQUEST ARGUMENTS 🎀

• conn — the XCB connection to X11. your lil hotline to the server, your main character connection 💜
• provider — TODO: NOT YET DOCUMENTED. bestie the docs said "not yet" and then never came back 😭

---

🍓 REPLY FIELDS 🍓

• response_type — the type of this reply, which in this case is XCB_RANDR_LIST_PROVIDER_PROPERTIES. This field is also chillin' inside the xcb_generic_reply_t, and you can use it to tell replies apart from each other — it's basically the reply's little name tag 🏷️
• sequence — the sequence number of the last request processed by the X11 server.
• length — the length of the reply, in words (and a word is 4 bytes, that's the lore, iykyk).
• num_atoms — TODO: NOT YET DOCUMENTED. once again, un-documented, we simply don't know 💀

---

🌈 DESCRIPTION 🌈

There is literally no description. The section exists and it's empty. Not me reading an empty section and respecting it fr fr 🙈✨

---

👑 RETURN VALUE 👑

Returns an xcb_randr_list_provider_properties_cookie_t. Cookies are iconic because they let you fire the request now and grab the answer later — but heads up, errors have to be handled when you call the reply function xcb_randr_list_provider_properties_reply.

If you'd rather handle errors in the event loop instead, use xcb_randr_list_provider_properties_unchecked. See xcb-requests(3) for the details on how that whole deal works 🫶

---

💀 ERRORS 💀

This request does never generate any errors. zero. none. clean sheet. slay.

---

🧚 SEE ALSO 🧚

Okay so this section is technically empty — the heading is there but there's not a single reference under it. Nothing to link, nothing to chase, no crumbs. 🍽️

---

💜 AUTHOR 💜

Generated from randr.xml. Contact xcb@lists.freedesktop.org for corrections and improvements — they're literally asking for your feedback, so if something's off, tell them, bestie, that's the assignment 📬

---

and that's the whole page!! no cap, every field, every accessor, every TODO that the maintainers ghosted us on — all accounted for 💅

X Version 11 · libxcb 1.17.0 — that's the source and version of this lil manual, periodt. take care of your providers, drink water, and may all your replies be error-free 🌸✨🦋