XCB_XFIXES_SELECT_SELECTION_INPUT_CHECKED(3)

💖 xcb_xfixes_select_selection_input — bestie edition 💖

okay so we're deep in libxcb, section 3 of the manual, and today's main character is a request function from the XCB XFixes era. yes it's real, yes it's libxcb 1.17.0, no cap. let's get into it 🦋

---

✨ NAME ✨

xcb_xfixes_select_selection_input — and that's literally all the original says, bestie. no little tagline, no nothing. it's giving mysterious. we move. 💅

---

✨ SYNOPSIS ✨

first things first, you gotta pull in the header:

#include <xcb/xfixes.h>

🎀 Request function 🎀

and here's the function itself, exactly as it lives, no edits, periodt:

xcb_void_cookie_t
       xcb_xfixes_select_selection_input(xcb_connection_t *conn,
       xcb_window_t window, xcb_atom_t selection, uint32_t event_mask);

look at her. four args, one xcb_void_cookie_t return, absolute icon. 👑

---

✨ REQUEST ARGUMENTS ✨

every single one, in order, no skips:

• conn — the XCB connection to X11. your lil lifeline to the server, fr fr 🫶
• window — TODO: NOT YET DOCUMENTED. yeah. the docs said "we'll get to it" and then never did. iconic of them honestly 😭
• selection — TODO: NOT YET DOCUMENTED. same energy. still undocumented. still mysterious. we stan a mystery 🕵️♀️
• event_mask — TODO: NOT YET DOCUMENTED. the whole trio is undoc'd bestie, I'm not making anything up here, I promise 💀

---

✨ DESCRIPTION ✨

so, um. the description section is... empty. there is literally nothing under it. it's giving silence. it's giving "we left this part blank on purpose." the vibe check came back and the vibe is vibes only, no text. 🌸

no extra lore, no secret paragraph, nothing. what you see is what you get. 🙈

---

✨ RETURN VALUE ✨

she returns an xcb_void_cookie_t — that's your lil receipt, your claim ticket, your ✨proof of purchase✨. and here's the important part, bestie:

any errors (if there are any) have to be handled in the event loop. you don't get them handed to you at call time, that's not how this works.

but wait — if you'd rather handle errors directly instead of waiting around in the event loop, you use the checked twin:

• xcb_xfixes_select_selection_input_checked — use this one with xcb_request_check if you want to deal with errors right away, no event-loop detour 💅

and if you need the full deets on how checked vs. unchecked works around here, go read xcb-requests(3). it explains everything, and I mean everything. 📖

---

✨ ERRORS ✨

good news, angel: this request does never generate any errors.

like, zero. none. not a single one. she's a clean girl, she's unproblematic, she's never once been the source of drama. 🌈

---

✨ SEE ALSO ✨

...and that's it. there are no cross-references listed. nothing. just vibes and emptiness. if you were hoping for a little "go look at this other page" moment, nope, the section's blank. 🎀

---

✨ AUTHOR ✨

this whole thing was generated from xfixes.xml. so if you spot something wrong and you wanna fix it or make it better, you hit up:

• xcb@lists.freedesktop.org

that's the address for corrections and improvements. be nice, be specific, be a good citizen. 💜

---

quick reminder bestie: I kept every single line here — the TODO: NOT YET DOCUMENTED. bits included — because those are the facts. I didn't invent behaviour, I didn't guess what window or selection do, and I didn't fill in the empty DESCRIPTION or SEE ALSO with fanfiction. that's the whole point. 🫶

---

and that's the page, babes. X Version 11, libxcb 1.17.0 — the date line up top was giving cryptic and honestly a little unreadable, so I'm just telling you straight: that's the source and version, and that's the era we're in. now go forth, compile something cute, and handle those errors in the event loop. mwah 💋✨