XCB_XFIXES_GET_CLIENT_DISCONNECT_MODE(3)

✨ NAME ✨

xcb_xfixes_get_client_disconnect_mode — bestie, the original page literally leaves the description blank here, so we're just gonna hold hands and vibe with the function name itself 💖

---

🌸 SYNOPSIS 🌸

First things first, you gotta pull in the header:

#include <xcb/xfixes.h>

🎀 Request function

xcb_xfixes_get_client_disconnect_mode_cookie_t
       xcb_xfixes_get_client_disconnect_mode(xcb_connection_t *conn,

🦋 Reply datastructure

typedef struct xcb_xfixes_get_client_disconnect_mode_reply_t {
    uint8_t  response_type;
    uint8_t  pad0;
    uint16_t sequence;
    uint32_t length;
    uint32_t disconnect_mode;
    uint8_t  pad1[20];
} xcb_xfixes_get_client_disconnect_mode_reply_t;

💅 Reply function

xcb_xfixes_get_client_disconnect_mode_reply_t
       *xcb_xfixes_get_client_disconnect_mode_reply(xcb_connection_t *conn,
       xcb_xfixes_get_client_disconnect_mode_cookie_t cookie,
       xcb_generic_error_t **e);

---

💜 REQUEST ARGUMENTS 💜

• conn — your XCB connection to X11. that's the whole list. one (1) argument, iconic behaviour honestly 👑

---

🌈 REPLY FIELDS 🌈

• response_type — the type of this reply, which in this case is XCB_XFIXES_GET_CLIENT_DISCONNECT_MODE. it also lives inside xcb_generic_reply_t, so you can use it to tell your replies apart from each other, no cap 🔍
• sequence — the sequence number of the last request the X11 server actually processed. it's giving "receipt of what the server has done so far" 🧾
• length — how long the reply is, counted in words. and bestie, a word here is 4 bytes, don't forget 📏
• disconnect_mode — the current disconnect mode. that's the tea you came for 🍓

---

✨ DESCRIPTION ✨

(okay so the original page has this section with literally nothing under it — no description, no lore, nothing. so there's nothing extra for me to tell you here, and I'm not about to make stuff up 💀)

---

🫶 RETURN VALUE 🫶

It hands you back an xcb_xfixes_get_client_disconnect_mode_cookie_t. Cookies are cute but errors are not, and you have to deal with those errors when you call the reply function, xcb_xfixes_get_client_disconnect_mode_reply. 🍪

If you'd rather handle your errors in the event loop instead, then use xcb_xfixes_get_client_disconnect_mode_unchecked and go off. See xcb-requests(3) for all the deets.

---

😭 ERRORS 😭

This request never generates any errors. not one. zero. a whole clean slate, we love that for it 🌸✨

---

👑 SEE ALSO 👑

(empty in the original, so… nothing to link, nothing to see, just vibes 🦋)

---

💖 AUTHOR 💖

Generated from xfixes.xml. If you spot something wrong or wanna make it better, hit up xcb@lists.freedesktop.org for corrections and improvements. go off, king 📧

---

okay that's the whole page bestie, you understood all of it, periodt 💅

and as a little sign-off — this one comes from X Version 11, libxcb 1.17.0, mwah, love that for us 🎀💜