XCB_INPUT_SET_DEVICE_MODIFIER_MAPPING_UNCHECKED(3)
π NAME π
xcb_input_set_device_modifier_mapping β okay bestie, so the manpage literally gives no one-liner here, it's just vibes and a blank space π the function name is the whole description fr fr.
β¨ SYNOPSIS β¨
First things first, you gotta pull in the header:
#include <xcb/xinput.h>
π Request function
xcb_input_set_device_modifier_mapping_cookie_t
xcb_input_set_device_modifier_mapping(xcb_connection_t *conn,
uint8_t device_id, uint8_t keycodes_per_modifier, const
uint8_t *keymaps);
π¦ Reply datastructure
typedef struct xcb_input_set_device_modifier_mapping_reply_t {
uint8_t response_type;
uint8_t xi_reply_type;
uint16_t sequence;
uint32_t length;
uint8_t status;
uint8_t pad0[23];
} xcb_input_set_device_modifier_mapping_reply_t;
πΈ Reply function
xcb_input_set_device_modifier_mapping_reply_t
*xcb_input_set_device_modifier_mapping_reply(xcb_connection_t *conn,
xcb_input_set_device_modifier_mapping_cookie_t cookie,
xcb_generic_error_t **e);
π REQUEST ARGUMENTS π
connβ the XCB connection to X11, your lil hotline to the server πdevice_idβ TODO: NOT YET DOCUMENTED. bestie the docs really said "figure it out" πkeycodes_per_modifierβ TODO: NOT YET DOCUMENTED. same energy, no notes, just mystery β¨keymapsβ TODO: NOT YET DOCUMENTED. iconic of them to leave us hanging fr fr
π REPLY FIELDS π
response_typeβ the type of this reply, and in this case it'sXCB_INPUT_SET_DEVICE_MODIFIER_MAPPING. This field also shows up in thexcb_generic_reply_t, so you can use it to tell your replies apart from each other πsequenceβ the sequence number of the last request the X11 server processed π«Άlengthβ how long the reply is, in words (and a word here is 4 bytes, periodt)xi_reply_typeβ TODO: NOT YET DOCUMENTED. the mystery continues π΅οΈstatusβ TODO: NOT YET DOCUMENTED. ngl we simply do not know π
π« DESCRIPTION π«
Okay soβ¦ there is genuinely nothing here. The section exists, the section is empty. It's giving minimalism, it's giving "no thoughts, head empty" π the vibe is immaculate, the content is zero.
π₯ RETURN VALUE π₯
You get back an xcb_input_set_device_modifier_mapping_cookie_t. Errors have to be handled when you call the reply function xcb_input_set_device_modifier_mapping_reply.
If you'd rather handle your errors in the event loop instead, use xcb_input_set_device_modifier_mapping_unchecked. Peep xcb-requests(3) for the deets, iykyk π
π ERRORS π
Good news bestie: this request does never generate any errors. Not one. Zero. Clean sheet. Slay. π
β SEE ALSO β
Nothing listed here, so likeβ¦ go forth and explore on your own, main character π¦
π AUTHOR π
Generated from xinput.xml. Wanna send corrections or improvements? Contact xcb@lists.freedesktop.org π
And that's a wrap, my love β this lil page came to you from X Version 11, libxcb 1.17.0. Go forth and map those modifiers, you absolute icon πβ¨πΈ
π¦ 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