XCB_SELINUX_SET_WINDOW_CREATE_CONTEXT_CHECKED(3)

πŸ“¦
version 1.17.0 Β· 4 versions
, in alpine 3.22, alpine 3.23, alpine 3.24, arch rolling, centos-stream 10, debian trixie, fedora 43, fedora 44, nixpkgs unstable, opensuse-leap 16.0, ubuntu questing, ubuntu resolute, ubuntu stonking

πŸ’– 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 says TODO: NOT YET DOCUMENTED. So that's what we know, and that's all we know. 🫠
  • context β€” also TODO: 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 πŸ’‹πŸ¦‹πŸŒΈ