xcb_xevie_select_input(3)
πΈ xcb_xevie_select_input πΈ
okay bestie, gather round, because we're looking at a page from XCB Requests β the xcb_xevie_select_input manual, to be exact. yes it's a mouthful, no you don't have to say it out loud. it lives in the libxcb world and it's one of those "small but mighty" request pages. let's get into it π
β¨ NAME β¨
xcb_xevie_select_input β and that's literally it, the description slot is empty, the void, the silence. iconic behaviour honestly. it's the XEvIE "select input" request and we move on π«Ά
π¦ SYNOPSIS π¦
first things first, you gotta bring in the header:
#include <xcb/xevie.h>
π Request function π
xcb_xevie_select_input_cookie_t
xcb_xevie_select_input(xcb_connection_t *conn,
uint32_t event_mask);
π Reply datastructure π
typedef struct xcb_xevie_select_input_reply_t {
uint8_t response_type;
uint8_t pad0;
uint16_t sequence;
uint32_t length;
uint8_t pad1[24];
} xcb_xevie_select_input_reply_t;
π Reply function π
xcb_xevie_select_input_reply_t
*xcb_xevie_select_input_reply(xcb_connection_t *conn,
xcb_xevie_select_input_cookie_t cookie, xcb_generic_error_t **e);
π REQUEST ARGUMENTS π
connβ the XCB connection to X11. your lil phone line to the server, no cap βοΈevent_maskβTODO: NOT YET DOCUMENTED.yeah. that's the whole thing. the docs said "we'll get to it" and then did not get to it π not me reading a TODO in a real manpage fr fr
β REPLY FIELDS β
response_typeβ the type of this reply, which in this case isXCB_XEVIE_SELECT_INPUT. this field is also chillin' inside thexcb_generic_reply_t, so you can use it to tell replies apart from each other. it's giving "name tag at the party" π·οΈsequenceβ the sequence number of the last request processed by the X11 server. lowkey the receipts of who did what and when πlengthβ the length of the reply, in words. and reminder bestie: a word is 4 bytes. periodt.
π§ DESCRIPTION π§
nothing here. empty. a blank space. the page simply does not describe it. we respect the mystery π
π RETURN VALUE π
so this one returns an xcb_xevie_select_input_cookie_t. a cookie!! πͺ and like any good cookie, the errors are a whole separate thing β you have to handle them when you call the reply function, xcb_xevie_select_input_reply.
and if you'd rather catch your errors in the event loop instead of at reply time, you use xcb_xevie_select_input_unchecked instead. see xcb-requests(3) for the deets, because that page has the whole explanation and I am not about to make things up β¨
π₯ ERRORS π₯
good news, bestie: this request does never generate any errors. zero. none. clean run, main character energy, we love to see it π
π¦ SEE ALSO π¦
nothing listed. the "see also" section is out here with no plans and no commitments. respect πΈ
π AUTHOR π
Generated from xevie.xml. want corrections or improvements? contact xcb@lists.freedesktop.org β they're the ones who can actually do something about it, not me π
and that's the whole page, bestie, you ate it π«Ά this was xcb_xevie_select_input(3) from X Version 11, libxcb 1.17.0 β go forth, select some input, and stay iconic π
β¨π
π¦ where this page comes from
- alpine 3.22: libxcb-doc 1.17.0-r0 Β· MIT
- alpine 3.23: libxcb-doc 1.17.0-r1 Β· MIT
- alpine 3.24: libxcb-doc 1.17.0-r2 Β· MIT
- arch rolling: libxcb 1.17.0-1 Β· X11
- centos-stream 10: libxcb-devel 1.17.0-3.el10 Β· X11
- debian trixie: libxcb-doc 1.17.0-2
- fedora 43: libxcb-devel 1.17.0-6.fc43 Β· X11
- fedora 43: libxcb-devel 1.17.0-6.fc43 Β· X11
- fedora 44: libxcb-devel 1.17.0-7.fc44 Β· X11
- fedora 44: libxcb-devel 1.17.0-7.fc44 Β· X11
- nixpkgs unstable: libxcb 1.17.0
- opensuse-leap 16.0: libxcb-devel-doc 1.17.0-160000.2.2 Β· MIT
- ubuntu questing: libxcb-doc 1.17.0-2build1
- ubuntu resolute: libxcb-doc 1.17.0-2ubuntu1
- ubuntu stonking: libxcb-doc 1.17.0-2ubuntu1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms