XCB_RES_QUERY_CLIENT_RESOURCES_TYPES(3)

💖 xcb_res_query_client_resources — XCB Requests 💖

okay bestie, gather round, because today we're reading a libxcb manpage and honestly? it's giving "function whose docs are a work in progress" and we're gonna love her anyway 🫶

so the manual this lives in is called XCB Requests, and the page you're holding is all about xcb_res_query_client_resources. that's it, that's the NAME section — no long description, no subtitle, just the name and a little dash trailing off into the void 💀 (the original really does leave it blank, i'm not hiding anything from you, promise)

---

✨ SYNOPSIS ✨

first thing you gotta do is pull in the header:

#include <xcb/res.h>

🌸 Request function

here's the actual call you'd make:

xcb_res_query_client_resources_cookie_t
       xcb_res_query_client_resources(xcb_connection_t *conn,
       uint32_t xid);

🌸 Reply datastructure

and here's the struct you get to stare at:

typedef struct xcb_res_query_client_resources_reply_t {
    uint8_t  response_type;
    uint8_t  pad0;
    uint16_t sequence;
    uint32_t length;
    uint32_t num_types;
    uint8_t  pad1[20];
} xcb_res_query_client_resources_reply_t;

🌸 Reply function

this is how you actually collect the reply:

xcb_res_query_client_resources_reply_t
       *xcb_res_query_client_resources_reply(xcb_connection_t *conn,
       xcb_res_query_client_resources_cookie_t cookie,
       xcb_generic_error_t **e);

🌸 Reply accessors

the little helper squad that digs the good stuff out for you ✨

xcb_res_type_t *xcb_res_query_client_resources_types(const
       xcb_res_query_client_resources_request_t *reply);

int xcb_res_query_client_resources_types_length(const
       xcb_res_query_client_resources_reply_t *reply);

xcb_res_type_iterator_t
       xcb_res_query_client_resources_types_iterator(const
       xcb_res_query_client_resources_reply_t *reply);

---

🎀 REQUEST ARGUMENTS 🎀

• conn — your XCB connection to X11, the whole reason you're here, the bestie that carries the message 💌
• xid — and this one? TODO: NOT YET DOCUMENTED. yeah. the original literally says that. iconic of them tbh 🙈

---

🦋 REPLY FIELDS 🦋

• response_type — tells you what kind of reply this is, and in this case it's XCB_RES_QUERY_CLIENT_RESOURCES. this field also lives inside xcb_generic_reply_t, so you can use it to tell your replies apart from each other 👑
• sequence — the sequence number of the last request the X11 server processed, aka the little timestamp of vibes ⭐
• length — how long the reply is, measured in words (and a word here is 4 bytes, don't forget, this trips people up fr fr)
• num_types — TODO: NOT YET DOCUMENTED. again!! the mystery continues 💀

---

🌈 DESCRIPTION 🌈

so... the DESCRIPTION section is empty. nothing. blank. not a single character. the void stared back and said nothing, and honestly? we respect the silence 🧚

---

💜 RETURN VALUE 💜

you get back an xcb_res_query_client_resources_cookie_t — cute little cookie, hold onto it 🍓

errors have to be handled when you call the reply function, xcb_res_query_client_resources_reply.

if you'd rather handle errors in the event loop instead, use xcb_res_query_client_resources_unchecked. check out xcb-requests(3) for the details, bestie, it's got the whole explanation.

---

🔥 ERRORS 🔥

this request does never generate any errors. zero. none. a perfectly behaved little angel 😇

---

🌟 SEE ALSO 🌟

the original page just leaves this heading sitting there all by itself — no references listed. so it's giving mysterious, it's giving "make of this what you will" 💅

---

👑 AUTHOR 👑

generated from res.xml. if you spot something wrong and wanna send corrections and improvements, hit up xcb@lists.freedesktop.org — they're literally asking, so don't be shy 🫶

---

and that's the whole page, babes! this one shipped with X Version 11, libxcb 1.17.0, in the XCB Requests manual — go forth and query those client resources, you absolute main character 💖✨🦋🌸🎀