XCB_RES_QUERY_CLIENT_PIXMAP_BYTES_REPLY(3)

💖 xcb_res_query_client_pixmap_bytes — the manual page, but make it make sense 💖

okay bestie, pull up a chair, because we're reading a libxcb page from the XCB Requests fam and honestly? it's giving "the docs left half the homework blank." but we're gonna work with what we got, no cap. ✨

---

🌸 NAME 🌸

xcb_res_query_client_pixmap_bytes — and that's it. that's the whole name. the manpage literally just... stops. iconique of it, honestly. 💅

---

🦋 SYNOPSIS 🦋

first things first, you gotta bring in the header:

#include <xcb/res.h>

✨ Request function ✨

here's the lil guy you call to send the request off into the void:

xcb_res_query_client_pixmap_bytes_cookie_t
       xcb_res_query_client_pixmap_bytes(xcb_connection_t *conn,
       uint32_t xid);

🎀 Reply datastructure 🎀

and this is the struct that comes back at you — every field, verbatim, do not touch:

typedef struct xcb_res_query_client_pixmap_bytes_reply_t {
    uint8_t  response_type;
    uint8_t  pad0;
    uint16_t sequence;
    uint32_t length;
    uint32_t bytes;
    uint32_t bytes_overflow;
} xcb_res_query_client_pixmap_bytes_reply_t;

💜 Reply function 💜

and this is how you actually go get that reply, bestie:

xcb_res_query_client_pixmap_bytes_reply_t
       *xcb_res_query_client_pixmap_bytes_reply(xcb_connection_t *conn,
       xcb_res_query_client_pixmap_bytes_cookie_t cookie,
       xcb_generic_error_t **e);

---

👑 REQUEST ARGUMENTS 👑

• conn — your XCB connection to X11. the whole pipeline to the server, the main character of the operation. 🔥
• xid — and the docs say... TODO: NOT YET DOCUMENTED. yeah. that's it. that's the description. we know it's an id, we know it's a uint32_t, and beyond that the manpage is staying mysterious. 🙈

---

🌈 REPLY FIELDS 🌈

• response_type — what kind of reply this is. in this case it's XCB_RES_QUERY_CLIENT_PIXMAP_BYTES. this field also lives in xcb_generic_reply_t, so you can use it to tell your replies apart from each other when they're all just vibing in the same place. 💫
• sequence — the sequence number of the last request the X11 server processed. it's the server's little timestamp of "yeah I got to this point." ⭐
• length — how long the reply is, measured in words. and reminder bestie: a word is 4 bytes. ✨
• bytes — TODO: NOT YET DOCUMENTED. the mystery continues, we love an enigma. 🫶
• bytes_overflow — TODO: NOT YET DOCUMENTED. the sequel to the mystery. also undocumented. also iconic for it. 💀

---

🧚 DESCRIPTION 🧚

so... there is a DESCRIPTION section. and it is empty. completely, utterly blank. not a single word. it's giving "we made a section and forgot to fill it in," and honestly? relatable. no cap, that's just how this page is. 💖

---

💅 RETURN VALUE 💅

it hands you back an xcb_res_query_client_pixmap_bytes_cookie_t. cookies are for later, babes — errors have to be handled when you call the reply function xcb_res_query_client_pixmap_bytes_reply.

and if you'd rather catch your errors in the event loop instead of right at the reply? use xcb_res_query_client_pixmap_bytes_unchecked. the deets on all that are over in xcb-requests(3). 🌸

---

💀 ERRORS 💀

good news for once: this request never generates any errors. not a single one. zero. the vibes are immaculate. 🎀

---

🦄 SEE ALSO 🦄

...nothing here either bestie. the section exists and then simply does not elaborate. we move. 🍓

---

💜 AUTHOR 💜

Generated from res.xml. if you've got corrections or improvements, hit up xcb@lists.freedesktop.org. they're the ones who can fix it. ✨

---

and that's the whole page, bestie! 🫶 this absolute legend of a manpage is brought to you by X Version 11 and libxcb 1.17.0, and if you ever wondered why half the fields say TODO — now you know, and knowing is half the battle. slay, stay connected, and may your xids always resolve. 💖🌈✨👑