xcb_res_query_resource_bytes(3)

💖 xcb_res_query_resource_bytes 💖

okay so bestie, welcome to the XCB Requests section of the manual, and today's main character is xcb_res_query_resource_bytes(3). pull up a chair, grab a boba, we're doing X11 resource byte queries and we're doing them adorably. 🦋

---

✨ NAME ✨

xcb_res_query_resource_bytes —

ngl the original manpage left this part blank. empty. a whole void. so like… the name is the name, bestie, that's all we got. 💀

---

🌸 SYNOPSIS 🌸

first things first, you gotta pull in the header:

#include <xcb/res.h>

🎀 Request function

xcb_res_query_resource_bytes_cookie_t
       xcb_res_query_resource_bytes(xcb_connection_t *conn,
       uint32_t client, uint32_t num_specs, const
       xcb_res_resource_id_spec_t *specs);

🎀 Reply datastructure

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

🎀 Reply function

xcb_res_query_resource_bytes_reply_t
       *xcb_res_query_resource_bytes_reply(xcb_connection_t *conn,
       xcb_res_query_resource_bytes_cookie_t cookie,
       xcb_generic_error_t **e);

🎀 Reply accessors

int xcb_res_query_resource_bytes_sizes_length(const
       xcb_res_query_resource_bytes_reply_t *reply);

xcb_res_resource_size_value_iterator_t
       xcb_res_query_resource_bytes_sizes_iterator(const
       xcb_res_query_resource_bytes_reply_t *reply);

---

👑 REQUEST ARGUMENTS 👑

• conn — the XCB connection to X11, obvi. your lil phone line to the server. 💅
• client — TODO: NOT YET DOCUMENTED. yeah bestie, they left us on read. 🙈
• num_specs — TODO: NOT YET DOCUMENTED. also left on read. 😭
• specs — TODO: NOT YET DOCUMENTED. the trio of mystery. iconic behaviour honestly.

---

🦋 REPLY FIELDS 🦋

• response_type — the type of this reply, which in this case is XCB_RES_QUERY_RESOURCE_BYTES. this field is also chillin' inside xcb_generic_reply_t, so you can use it to tell replies apart from each other. it's giving name tag at a party. 🎀
• sequence — the sequence number of the last request processed by the X11 server. the server's lil receipt number. 🧾
• length — the length of the reply, in words. and heads up, a word is 4 bytes. not a dictionary word. a byte word. iykyk. ⭐
• num_sizes — TODO: NOT YET DOCUMENTED. once again, the docs said "no thoughts, head empty". 💀

---

🌈 DESCRIPTION 🌈

literally nothing here, bestie. the DESCRIPTION section is empty. a blank canvas. the manpage equivalent of a notes app draft titled "ideas". 😭

---

💜 RETURN VALUE 💜

Returns an xcb_res_query_resource_bytes_cookie_t. 🍪

Errors have to be handled when you call the reply function xcb_res_query_resource_bytes_reply.

But wait — if you'd rather handle errors in the event loop instead, use xcb_res_query_resource_bytes_unchecked. see xcb-requests(3) for the deets. 🫶

---

🔥 ERRORS 🔥

This request does never generate any errors. not one. zero. flawless. no notes. periodt. 💅✨

---

🎀 SEE ALSO 🎀

the original left this section empty too. so… see also: nothing. see also: the void. see also: your own heart. 💖

---

💖 AUTHOR 💖

Generated from res.xml. if you've got corrections or improvements, hit up xcb@lists.freedesktop.org. they're literally asking, bestie, don't be shy. 🌸

---

okay and the lil sign-off at the bottom of the page said X Version 11 and libxcb 1.17.0, so there you have it — that's the vibe, that's the version, that's the whole page. mwah. 💋✨🦋