XCB_SELINUX_GET_CLIENT_CONTEXT_CONTEXT_LENGTH(3)

xcb_selinux_get_client_context 💅

okay bestie, welcome to the XCB Requests corner of the universe — this is the xcb_selinux_get_client_context(3) page and we are gonna get you fluent in it, no cap ✨

---

🌸 NAME 🌸

xcb_selinux_get_client_context — (yeah bestie, the original literally just leaves the dash hanging there, so that's what we're doing too, periodt)

---

✨ SYNOPSIS ✨

first things first, you gotta pull the header in:

#include <xcb/xselinux.h>

🦋 Request function

xcb_selinux_get_client_context_cookie_t
xcb_selinux_get_client_context(xcb_connection_t *conn,
                               uint32_t resource);

🎀 Reply datastructure

this is the lil struct the server hands back, look at her:

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

💖 Reply function

xcb_selinux_get_client_context_reply_t
*xcb_selinux_get_client_context_reply(xcb_connection_t *conn,
                                      xcb_selinux_get_client_context_cookie_t cookie,
                                      xcb_generic_error_t **e);

🌈 Reply accessors

these are the little helpers that go digging inside the reply for you:

char *xcb_selinux_get_client_context_context(const xcb_selinux_get_client_context_request_t *reply);

int xcb_selinux_get_client_context_context_length(const xcb_selinux_get_client_context_reply_t *reply);

xcb_generic_iterator_t xcb_selinux_get_client_context_context_end(const xcb_selinux_get_client_context_reply_t *reply);

---

🫶 REQUEST ARGUMENTS 🫶

• conn — the XCB connection to X11. she's your link to the server, your main character connection, fr fr 🔥
• resource — TODO: NOT YET DOCUMENTED. (the docs really said "we'll figure it out later" and honestly? relatable 💀)

---

👑 REPLY FIELDS 👑

• response_type — the type of this reply, and in this specific case it's XCB_SELINUX_GET_CLIENT_CONTEXT. This field also lives inside xcb_generic_reply_t, so you can use it to tell replies apart from each other. it's giving name tag at a party 🎀
• sequence — the sequence number of the last request processed by the X11 server. receipts, basically 🧾✨
• length — the length of the reply, in words (and a word is 4 bytes, don't forget that part bestie).
• context_len — TODO: NOT YET DOCUMENTED. (again! the mystery continues 🙈)

---

💜 DESCRIPTION 💜

<nothing here, bestie — the original page leaves this section empty, so we're leaving it empty too. we respect the void 🕳️✨>

---

⭐ RETURN VALUE ⭐

She returns an xcb_selinux_get_client_context_cookie_t. Errors have to be handled when you call the reply function xcb_selinux_get_client_context_reply.

If you'd rather handle errors in the event loop instead, use xcb_selinux_get_client_context_unchecked. Peep xcb-requests(3) for the deets 🫶

---

💀 ERRORS 💀

This request does never generate any errors. not a single one. she's flawless, she's unbothered, she ate and left no crumbs 👑

---

🌟 SEE ALSO 🌟

nothing listed here in the original, bestie — the section is there, the vibes are there, the references are not 🦋

---

💌 AUTHOR 💌

Generated from xselinux.xml. Contact xcb@lists.freedesktop.org for corrections and improvements. (yes, real ones email the list, that's the group chat 💅)

---

and that's the whole page, bestie!! 🎀 This one came to you from X Version 11, libxcb 1.17.0 — mwah, slay, go forth and query those client contexts 💖✨🦋