XCB_INPUT_SET_DEVICE_MODIFIER_MAPPING_UNCHECKED(3)

πŸ“¦
version 1.17.0 Β· 4 versions
, in alpine 3.22, alpine 3.23, alpine 3.24, arch rolling, centos-stream 10, debian trixie, fedora 43, fedora 44, nixpkgs unstable, opensuse-leap 16.0, ubuntu questing, ubuntu resolute, ubuntu stonking

πŸ’– 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's XCB_INPUT_SET_DEVICE_MODIFIER_MAPPING. This field also shows up in the xcb_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 πŸ’–βœ¨πŸŒΈ