xcb_set_access_control(3)

💅 xcb_set_access_control — the libxcb manual page, bestie edition

okay so this is xcb_set_access_control from the XCB crew, part of X Version 11 / libxcb 1.17.0. Let's get into it 🦋

---

✨ NAME ✨

xcb_set_access_control — literally no description given, the manpage just trails off 💀

---

🌸 SYNOPSIS 🌸

#include <xcb/xproto.h>

🎀 Request function

xcb_void_cookie_t xcb_set_access_control(xcb_connection_t *conn,
       uint8_t mode);

---

🫶 REQUEST ARGUMENTS 🫶

• conn — your XCB connection to X11. the whole vibe conduit, yk?
• mode — one of the following values, bestie:
  • XCB_ACCESS_CONTROL_DISABLE — TODO: NOT YET DOCUMENTED.
  • XCB_ACCESS_CONTROL_ENABLE — TODO: NOT YET DOCUMENTED.

and then there's one more line that's just... TODO: NOT YET DOCUMENTED. all by itself. no label, no explanation. she's mysterious. she's giving main character energy. not me leaving a third TODO in the list 🙈

---

💜 DESCRIPTION 💜

the description section is... empty. completely empty. zero words. a whole void. 😭

---

⭐ RETURN VALUE ⭐

Returns an xcb_void_cookie_t, babes. Errors (if any) have to be handled in the event loop — so that's your job, not the function's 💅

If you want to handle errors directly with xcb_request_check instead, use xcb_set_access_control_checked. See xcb-requests(3) for details. iykyk 🔥

---

🌈 ERRORS 🌈

This request does never generate any errors. not one. zero. clean sheet. periodt 👑

---

🦋 SEE ALSO 🦋

nothing here either. the section is just... vibes. an empty little shelf. we respect her anyway 🎀

---

👑 AUTHOR 👑

Generated from xproto.xml. Contact xcb@lists.freedesktop.org for corrections and improvements. no cap, that's the whole credit line 💖

---

okay bestie that's the whole page, we ate and left no crumbs ✨ this was xcb_set_access_control(3) from X Version 11, libxcb 1.17.0 — catch you in the next manpage, mwah 🫶💅🌸