XCB_SELINUX_SET_WINDOW_CREATE_CONTEXT_CHECKED(3)
π xcb_selinux_set_window_create_context β the manual page, but make it make sense π
okay bestie, gather round, because we're reading a manual page from libxcb and it's giving "the docs said TODO and never came back" energy. The page you're on is xcb_selinux_set_window_create_context(3), and yes it lives in the XCB Requests corner of the world. Let's get into it π«Ά
β¨ NAME β¨
xcb_selinux_set_window_create_context β and thenβ¦ literally nothing. The description after that dash is empty in the original. Not me being lazy, that's just how the page ships. No cap. π
πΈ SYNOPSIS πΈ
First things first, you gotta pull in the header:
#include <xcb/xselinux.h>
π Request function π
xcb_void_cookie_t
xcb_selinux_set_window_create_context(xcb_connection_t *conn,
uint32_t context_len, const char *context);
That's the whole signature, character for character, slay. Notice it hands you back an xcb_void_cookie_t, so it's not giving you any payload back directly β more on that below π
π¦ REQUEST ARGUMENTS π¦
connβ the XCB connection to X11. Your little phone line to the X server, basically. πcontext_lenβ the original page saysTODO: NOT YET DOCUMENTED.So that's what we know, and that's all we know. π«contextβ alsoTODO: NOT YET DOCUMENTED.The manpage really said "figure it out" and dipped. π
real talk: I'm not gonna make stuff up about what these do, because inventing details would be lying to you and you deserve better than a fake manpage. If the page says TODO, it's TODO. periodt.
π DESCRIPTION π
This section is empty in the original. Nothing. A whole heading, zero content. It's giving minimalist, it's giving "the author had plans and then the weekend happened." β¨
π₯ RETURN VALUE π₯
You get back an xcb_void_cookie_t. And because it's void, any errors (if any) have to be handled in the event loop β that's the deal with these cookie situations, bestie. πͺ
If you'd rather handle errors directly with xcb_request_check instead, then use xcb_selinux_set_window_create_context_checked. See xcb-requests(3) for the details. That's the checked twin, the responsible sibling, the one who does their homework. π
π ERRORS π
This request does never generate any errors.
Iconic behaviour honestly. Zero drama, zero errors, just vibes. π
π SEE ALSO π
This section is empty in the original too. No cross-references, no friends, just this page floating alone in the void. π
π AUTHOR π
Generated from xselinux.xml. Contact xcb@lists.freedesktop.org for corrections and improvements β so if you spot something, email them, don't just scream into the group chat. π§
and that's the whole page, babe π the footer said X Version 11, libxcb 1.17.0, so that's your source-and-version tea for the day. go forth, link against it, and remember: even a manual page that's 80% TODO is still a manual page we love. mwah ππ¦πΈ
π¦ where this page comes from
- alpine 3.22: libxcb-doc 1.17.0-r0 Β· MIT
- alpine 3.23: libxcb-doc 1.17.0-r1 Β· MIT
- alpine 3.24: libxcb-doc 1.17.0-r2 Β· MIT
- arch rolling: libxcb 1.17.0-1 Β· X11
- centos-stream 10: libxcb-devel 1.17.0-3.el10 Β· X11
- debian trixie: libxcb-doc 1.17.0-2
- fedora 43: libxcb-devel 1.17.0-6.fc43 Β· X11
- fedora 43: libxcb-devel 1.17.0-6.fc43 Β· X11
- fedora 44: libxcb-devel 1.17.0-7.fc44 Β· X11
- fedora 44: libxcb-devel 1.17.0-7.fc44 Β· X11
- nixpkgs unstable: libxcb 1.17.0
- opensuse-leap 16.0: libxcb-devel-doc 1.17.0-160000.2.2 Β· MIT
- ubuntu questing: libxcb-doc 1.17.0-2build1
- ubuntu resolute: libxcb-doc 1.17.0-2ubuntu1
- ubuntu stonking: libxcb-doc 1.17.0-2ubuntu1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms