xcb_input_get...e_key_mapping(3)

💅 xcb_input_get...e_key_mapping — XCB Requests, bestie

okay so bestie, welcome to the manual page for xcb_input_get...e_key_mapping(3) — that's the XCB Requests one, in case you were wondering which manual you just opened. it's giving "libxcb's xinput corner" and honestly? we're obsessed. this is where you go when you need to ask the X server "hey queen, what keysyms live on this device's keycodes?" 🎀

---

🌸 NAME 🌸

xcb_input_get_device_key_mapping — (no description in the original, it just is, iconic behaviour, no notes 💅)

---

✨ SYNOPSIS ✨

#include <xcb/xinput.h>

🦋 Request function 🦋

xcb_input_get_device_key_mapping_cookie_t
       xcb_input_get_device_key_mapping(xcb_connection_t *conn,
       uint8_t device_id, xcb_input_key_code_t first_keycode,
       uint8_t count);

🦋 Reply datastructure 🦋

typedef struct xcb_input_get_device_key_mapping_reply_t {
    uint8_t  response_type;
    uint8_t  xi_reply_type;
    uint16_t sequence;
    uint32_t length;
    uint8_t  keysyms_per_keycode;
    uint8_t  pad0[23];
} xcb_input_get_device_key_mapping_reply_t;

🦋 Reply function 🦋

xcb_input_get_device_key_mapping_reply_t
       *xcb_input_get_device_key_mapping_reply(xcb_connection_t *conn,
       xcb_input_get_device_key_mapping_cookie_t cookie,
       xcb_generic_error_t **e);

🦋 Reply accessors 🦋

xcb_keysym_t *xcb_input_get_device_key_mapping_keysyms(const
       xcb_input_get_device_key_mapping_request_t *reply);

int xcb_input_get_device_key_mapping_keysyms_length(const
       xcb_input_get_device_key_mapping_reply_t *reply);

xcb_generic_iterator_t
       xcb_input_get_device_key_mapping_keysyms_end(const
       xcb_input_get_device_key_mapping_reply_t *reply);

---

🔥 REQUEST ARGUMENTS 🔥

• conn — the XCB connection to X11. your lil hotline to the server, periodt 💖
• device_id — TODO: NOT YET DOCUMENTED. (the docs said "figure it out" and honestly, same 😭)
• first_keycode — TODO: NOT YET DOCUMENTED. (mystery behaviour, we love a secretive king 🙈)
• count — TODO: NOT YET DOCUMENTED. (again, no notes, the docs are gatekeeping 💀)

---

👑 REPLY FIELDS 👑

• response_type — the type of this reply, and in this case it's XCB_INPUT_GET_DEVICE_KEY_MAPPING. this field is also present in the xcb_generic_reply_t and can be used to tell replies apart from each other. it's basically the reply's little name tag at the function, so you know who's who 🫶
• sequence — the sequence number of the last request processed by the X11 server. the timeline, fr fr ⭐
• length — the length of the reply, in words (a word is 4 bytes). math girlies rise 🧚
• xi_reply_type — TODO: NOT YET DOCUMENTED. (undocumented and unbothered 💜)
• keysyms_per_keycode — TODO: NOT YET DOCUMENTED. (the mystery continues, lowkey iconic 🌈)

---

💖 DESCRIPTION 💖

(that's it. that's the description. the original literally left this blank — main character energy, saying nothing and letting the vibes speak 🎀)

---

🌟 RETURN VALUE 🌟

Returns an xcb_input_get_device_key_mapping_cookie_t. Errors have to be handled when calling the reply function xcb_input_get_device_key_mapping_reply.

heads up bestie — if you want to handle errors in the event loop instead, use xcb_input_get_device_key_mapping_unchecked. see xcb-requests(3) for details. ✨

---

💀 ERRORS 💀

This request does never generate any errors. not one. zero. the drama-free queen we all aspire to be 💅

---

🎀 SEE ALSO 🎀

(empty in the original — it's giving "no thoughts, head empty," and we respect it 🦋)

---

🌸 AUTHOR 🌸

Generated from xinput.xml. Contact xcb@lists.freedesktop.org for corrections and improvements.

---

and that's the whole page, bestie!! 💖 this one came to you from X Version 11, libxcb 1.17.0, and it's filed under xcb_input_get...e_key_mapping(3). go forth and slay your key mappings, mwah 😘✨