xcb_x_print_p...ne_attributes(3)

🌸 NAME 🌸

xcb_x_print_print_get_one_attributes — bestie, the name is literally the whole description here, the original left it blank, so we're just gonna vibe with the function name 💅

---

✨ SYNOPSIS ✨

First things first, you gotta pull in the header, no cap:

#include <xcb/xprint.h>

🦋 Request function 🦋

xcb_x_print_print_get_one_attributes_cookie_t
       xcb_x_print_print_get_one_attributes(xcb_connection_t *conn,
       xcb_x_print_pcontext_t context, uint32_t nameLen, uint8_t pool,
       const xcb_x_print_string8_t *name);

🎀 Reply datastructure 🎀

Okay so this is the struct that comes back at you, iconic:

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

💖 Reply function 💖

xcb_x_print_print_get_one_attributes_reply_t
       *xcb_x_print_print_get_one_attributes_reply(xcb_connection_t *conn,
       xcb_x_print_print_get_one_attributes_cookie_t cookie,
       xcb_generic_error_t **e);

🌈 Reply accessors 🌈

These are your lil grabby-hands helpers for digging into the reply, obsessed:

xcb_x_print_string8_t *xcb_x_print_print_get_one_attributes_value(const
       xcb_x_print_print_get_one_attributes_request_t *reply);

int xcb_x_print_print_get_one_attributes_value_length(const
       xcb_x_print_print_get_one_attributes_reply_t *reply);

xcb_generic_iterator_t
       xcb_x_print_print_get_one_attributes_value_end(const
       xcb_x_print_print_get_one_attributes_reply_t *reply);

👀 heads up bestie, the _value accessor takes a xcb_x_print_print_get_one_attributes_request_t * while the other two take xcb_x_print_print_get_one_attributes_reply_t *. That's literally how it is, don't come for me.

---

🫶 REQUEST ARGUMENTS 🫶

• conn — your XCB connection to X11, the whole main character of the situation 💫
• context — TODO: NOT YET DOCUMENTED. yeah girl, the docs said nothing 😭
• nameLen — TODO: NOT YET DOCUMENTED. also nothing 🙈
• pool — TODO: NOT YET DOCUMENTED. silence 💀
• name — TODO: NOT YET DOCUMENTED. still silence 🍓

---

👑 REPLY FIELDS 👑

• response_type — the type of this reply, which in this case is XCB_X_PRINT_PRINT_GET_ONE_ATTRIBUTES. This field also lives inside xcb_generic_reply_t, so you can use it to tell your replies apart from each other. it's giving name tag at a party ✨
• sequence — the sequence number of the last request the X11 server processed 🔢
• length — how long the reply is, in words (and a word is 4 bytes, fyi) 📏
• valueLen — TODO: NOT YET DOCUMENTED. the mystery continues 🕵️♀️

---

💜 DESCRIPTION 💜

Nothing here. Empty. A whole section of absolutely nothing, and honestly? that's its own kind of iconic 🌸

---

⭐ RETURN VALUE ⭐

You get back an xcb_x_print_print_get_one_attributes_cookie_t. Errors? You have to handle those when you call the reply function xcb_x_print_print_get_one_attributes_reply, periodt.

If you'd rather handle errors in the event loop instead, use xcb_x_print_print_get_one_attributes_unchecked. Go peek at xcb-requests(3) for the deets 🫶

---

💀 ERRORS 💀

This request does never generate any errors. not a single one. zero drama, we love that for us 🎀

---

🔥 SEE ALSO 🔥

(nothing listed here, bestie — the section exists but it's just vibes and empty space 🦋)

---

🌟 AUTHOR 🌟

Generated from xprint.xml. Got corrections or improvements? Contact xcb@lists.freedesktop.org — they're the ones to @ 💌

---

okay that's the whole page, ily, go write some X Print code 🌈💅

X Version 11 · libxcb 1.17.0 · xcb_x_print_p...ne_attributes(3) — mwah, signing off 🎀✨