xcb_xkb_get_indicator_state(3)
π xcb_xkb_get_indicator_state β the whole manual, bestie π
okay so bestie, we're looking at xcb_xkb_get_indicator_state(3) from the XCB Requests crew. yes that's the manual name, no I will not be saying it three times fast. let's get into it π
β¨ NAME β¨
xcb_xkb_get_indicator_state β and that's literally it. the og page leaves the description blank, so likeβ¦ the name is the name. iconic behaviour tbh. π
β¨ SYNOPSIS β¨
first things first, you gotta pull in the header:
#include <xcb/xkb.h>
π¦ Request function
xcb_xkb_get_indicator_state_cookie_t
xcb_xkb_get_indicator_state(xcb_connection_t *conn,
xcb_xkb_device_spec_t deviceSpec);
π¦ Reply datastructure
typedef struct xcb_xkb_get_indicator_state_reply_t {
uint8_t response_type;
uint8_t deviceID;
uint16_t sequence;
uint32_t length;
uint32_t state;
uint8_t pad0[20];
} xcb_xkb_get_indicator_state_reply_t;
π¦ Reply function
xcb_xkb_get_indicator_state_reply_t
*xcb_xkb_get_indicator_state_reply(xcb_connection_t *conn,
xcb_xkb_get_indicator_state_cookie_t cookie,
xcb_generic_error_t **e);
πΈ REQUEST ARGUMENTS πΈ
connβ your XCB connection to X11. the whole link to the server, the vibe carrier, the moment. β¨deviceSpecβ okay soβ¦ the original literally saysTODO: NOT YET DOCUMENTED.π bestie they left it blank. no cap. I'm not gonna make something up because that would be lying and lying is not the move. π
π REPLY FIELDS π
response_typeβ the type of this reply, and in this case it'sXCB_XKB_GET_INDICATOR_STATE. this field is also chillin' insidexcb_generic_reply_t, so you can use it to tell your replies apart from each other. like name tags at a party but for packets. πsequenceβ the sequence number of the last request the X11 server processed. the receipts, basically. π§Ύlengthβ how long the reply is, in words. and a word here is 4 bytes, so don't come at it with your English-major definition of "word". πdeviceIDβTODO: NOT YET DOCUMENTED.yeah. blank again. πstateβTODO: NOT YET DOCUMENTED.three for three, the og page said nothing, and I respect the mystery honestly. β¨
π DESCRIPTION π
this section is empty in the original. like, genuinely empty. nothing. void. the silence is deafening fr fr. so I have nothing to tell you here and I'm not about to invent lore. π«Ά
β RETURN VALUE β
so this one returns an xcb_xkb_get_indicator_state_cookie_t. and listen β errors have to be handled when you call the reply function xcb_xkb_get_indicator_state_reply. that's the deal, bestie.
but if you'd rather handle errors in the event loop instead? use xcb_xkb_get_indicator_state_unchecked. see xcb-requests(3) for the details on how that whole thing works. π₯
π ERRORS π
the tea: this request never generates any errors. zero. none. not a single one. it's giving peaceful. ποΈ
π§ SEE ALSO π§
(nothing listed in the original β this section is empty too. the og page is a minimalist, and honestly? main character energy.) π
π AUTHOR π
Generated from xkb.xml. got corrections or improvements? contact xcb@lists.freedesktop.org β they're the ones to slide into the inbox of. π¬
and that's the whole thing, bestie!! this page came to you from X Version 11, libxcb 1.17.0 β mwah, slay, go read the source, periodt. πβ¨ππ¦
π¦ 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