xcb_xf86dri_g...t_driver_name(3)

💖 xcb_xf86dri_get_client_driver_name — bestie edition 💖

okay so this is a page from section 3 of the manual (that's the library-calls section, iykyk), and it's one of the XCB Requests. It's been sitting in libxcb 1.17.0 on X Version 11 this whole time and honestly? nobody ever gave it a glow-up. so here we are. 🦋

---

✨ NAME ✨

xcb_xf86dri_get_client_driver_name — and then… literally a dash. that's it. that's the description. the manpage authors said "no thoughts, head empty" and left us a lonely little -. iconic behaviour, honestly. 💅

---

🌸 SYNOPSIS 🌸

First things first, you gotta let the compiler know:

#include <xcb/xf86dri.h>

🎀 Request function 🎀

xcb_xf86dri_get_client_driver_name_cookie_t
       xcb_xf86dri_get_client_driver_name(xcb_connection_t *conn,
       uint32_t screen);

🎀 Reply datastructure 🎀

not me being obsessed with a struct. look at her:

typedef struct xcb_xf86dri_get_client_driver_name_reply_t {
    uint8_t  response_type;
    uint8_t  pad0;
    uint16_t sequence;
    uint32_t length;
    uint32_t client_driver_major_version;
    uint32_t client_driver_minor_version;
    uint32_t client_driver_patch_version;
    uint32_t client_driver_name_len;
    uint8_t  pad1[8];
} xcb_xf86dri_get_client_driver_name_reply_t;

🎀 Reply function 🎀

xcb_xf86dri_get_client_driver_name_reply_t
       *xcb_xf86dri_get_client_driver_name_reply(xcb_connection_t *conn,
       xcb_xf86dri_get_client_driver_name_cookie_t cookie,
       xcb_generic_error_t **e);

🎀 Reply accessors 🎀

char *xcb_xf86dri_get_client_driver_name_client_driver_name(const
       xcb_xf86dri_get_client_driver_name_request_t *reply);

int xcb_xf86dri_get_client_driver_name_client_driver_name_length(const
       xcb_xf86dri_get_client_driver_name_reply_t *reply);

xcb_generic_iterator_t
       xcb_xf86dri_get_client_driver_name_client_driver_name_end(const
       xcb_xf86dri_get_client_driver_name_reply_t *reply);

---

🫶 REQUEST ARGUMENTS 🫶

• conn — the XCB connection to X11. your lil phone line to the server, basically. 📞
• screen — TODO: NOT YET DOCUMENTED. yeah bestie, the manpage itself is leaving us on read. 🙈

---

💜 REPLY FIELDS 💜

• response_type — the type of this reply, which in this case is XCB_XF86DRI_GET_CLIENT_DRIVER_NAME. this field is also chilling inside xcb_generic_reply_t, and you use it to tell your replies apart from each other. it's giving name-tag energy. 🏷️
• sequence — the sequence number of the last request processed by the X11 server. ✨
• length — the length of the reply, measured in words. and a word here is 4 bytes, no cap. 📏
• client_driver_major_version — TODO: NOT YET DOCUMENTED. 🫠
• client_driver_minor_version — TODO: NOT YET DOCUMENTED. 🫠
• client_driver_patch_version — TODO: NOT YET DOCUMENTED. 🫠
• client_driver_name_len — TODO: NOT YET DOCUMENTED. 🫠

four whole TODOs in one struct… the lore is simply not there yet. don't make stuff up about them, okay? we respect the mystery. 🔥

---

🌈 DESCRIPTION 🌈

…and that's it. that's the section. it's empty. the DESCRIPTION has no description. main character with no backstory, we love that for her. 💀

---

👑 RETURN VALUE 👑

So it returns an xcb_xf86dri_get_client_driver_name_cookie_t. 🍪

Errors? You handle those when you call the reply function xcb_xf86dri_get_client_driver_name_reply.

But if you'd rather handle errors in the event loop instead, use xcb_xf86dri_get_client_driver_name_unchecked. See xcb-requests(3) for the details, bestie. ✨

---

💅 ERRORS 💅

This request does never generate any errors. periodt. flawless, error-free, unbothered. 💖

---

🔥 SEE ALSO 🔥

(also empty. the manpage is really out here giving minimalism. nothing to link, nothing to see, no cap. 🦋)

---

🧚 AUTHOR 🧚

Generated from xf86dri.xml. Contact xcb@lists.freedesktop.org for corrections and improvements. (yes, they want your feedback. they're literally asking. go say hi. 🫶)

---

that's the whole page, babe — X Version 11, libxcb 1.17.0, and the header title xcb_xf86dri_g...t_driver_name(3) up top in case you need to cite her. mwah. 💋✨🌸