xcb_x_print_p...nput_selected(3)

💖 NAME 💖

xcb_x_print_print_input_selected — okay so bestie, this is the request that tells the X print server which input you've selected, and it literally has no description text in the original docs. We're working with what we've got. 🫶

---

✨ SYNOPSIS ✨

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

#include <xcb/xprint.h>

🎀 Request function

xcb_x_print_print_input_selected_cookie_t
       xcb_x_print_print_input_selected(xcb_connection_t *conn,
       xcb_x_print_pcontext_t context);

🦋 Reply datastructure

This is the lil struct that comes back at you:

typedef struct xcb_x_print_print_input_selected_reply_t {
    uint8_t  response_type;
    uint8_t  pad0;
    uint16_t sequence;
    uint32_t length;
    uint32_t event_mask;
    uint32_t all_events_mask;
} xcb_x_print_print_input_selected_reply_t;

🌸 Reply function

xcb_x_print_print_input_selected_reply_t
       *xcb_x_print_print_input_selected_reply(xcb_connection_t *conn,
       xcb_x_print_print_input_selected_cookie_t cookie,
       xcb_generic_error_t **e);

---

🍓 REQUEST ARGUMENTS 🍓

• conn — the XCB connection to X11. Your whole little line to the server, basically. 💅
• context — TODO: NOT YET DOCUMENTED. Yeah bestie, they left us on read with this one. 🙈

---

👑 REPLY FIELDS 👑

• response_type — the type of this reply, and in this specific case it's XCB_X_PRINT_PRINT_INPUT_SELECTED. This field also lives inside the xcb_generic_reply_t, so you can use it to tell your replies apart from each other when they're all piled up. So useful. ⭐
• sequence — the sequence number of the last request processed by the X11 server. Receipts, fr fr. 🧾
• length — the length of the reply, measured in words. And just so we're clear: a word is 4 bytes. Not a vibe, a byte count. ✨
• event_mask — TODO: NOT YET DOCUMENTED. 😭
• all_events_mask — TODO: NOT YET DOCUMENTED. 😭

---

🌈 DESCRIPTION 🌈

Genuinely nothing here. The original page leaves this section completely empty. Not me giving you a blank section, but also not me inventing lore that isn't in the docs. 💀

---

💜 RETURN VALUE 💜

It hands you back an xcb_x_print_print_input_selected_cookie_t. Now listen — errors have to be handled when you call the reply function, xcb_x_print_print_input_selected_reply. That's where they show up. Don't skip it. 🙏

But if you'd rather deal with your errors inside the event loop instead, use xcb_x_print_print_input_selected_unchecked. The details live in xcb-requests(3), go read it, it's giving required reading. 📚

---

🔥 ERRORS 🔥

This request never generates any errors. Not one. Zero. Iconic behaviour honestly. ✨

---

🎀 SEE ALSO 🎀

Empty in the original, bestie. Nothing to see here. 🦋

---

💖 AUTHOR 💖

Generated from xprint.xml. If you wanna send corrections or improvements, hit up xcb@lists.freedesktop.org. They're the ones who made this. 🫶

---

That's the whole page, bestie — every flag, field, and footnote accounted for, no skips, no invented lore. This one came from X Version 11, libxcb 1.17.0, and it's the xcb_x_print_p...nput_selected(3) page from XCB Requests. Slay, go forth and select your input. 💅🌈✨