XCB_SELINUX_SET_PROPERTY_CREATE_CONTEXT_CHECKED(3)
β¨ NAME β¨
xcb_selinux_set_property_create_context β bestie, that's the whole name, and the description slot is literally empty π (we'll get to why in a sec). This one lives in section 3 of the manual, so consider this your xcb_selinux_s...create_context(3) era π
π¦ SYNOPSIS π¦
First thing, the include. Don't forget it or you'll be sad:
#include <xcb/xselinux.h>
π Request function
xcb_void_cookie_t
xcb_selinux_set_property_create_context(xcb_connection_t *conn,
uint32_t context_len, const char *context);
That's the whole vibe. Three args, one void cookie, no cap β¨
π REQUEST ARGUMENTS π
connβ the XCB connection to X11. Your lil hotline to the X server, she's the main character here πcontext_lenβTODO: NOT YET DOCUMENTED.yeah. the docs said "we'll do it later" and then never did πcontextβ alsoTODO: NOT YET DOCUMENTED.twin flops fr fr π
Not me reading the manpage and getting two whole TODOs. They're in the original, so they're staying in. That's the rules bestie π«Ά
πΈ DESCRIPTION πΈ
Okay so here's the thing: this section is empty in the source. Like, genuinely nothing. No prose, no lore, no nothing. She's giving mysterious. She's giving "the documentation is a group project and nobody did their part" π
What we do know lives in the sections around it β the args, the return value, the error situation. Go read those. I got you β¨
π RETURN VALUE π
She hands you back an xcb_void_cookie_t π
Now listen, because this part matters: errors (if any) have to be handled in the event loop. So don't just take the cookie and ghost it β you've gotta actually check in the event loop, okay?
If you'd rather handle errors directly with xcb_request_check instead? Then use xcb_selinux_set_property_create_context_checked β note the _checked at the end, that's the one that'll give you the receipts π₯
For all the deets, go read xcb-requests(3). Periodt π
β ERRORS β
Good news era, actually:
This request does never generate any errors.
Zero. None. Not a single one. Iconic behaviour honestly π
π§ SEE ALSO π§
Also empty in the original. No cross-references listed, no friends tagged, she's solo in here πΈ
π AUTHOR π
Generated from xselinux.xml. So if something's wrong, it's not a human's fault, it's the XML's fault π
Want to fix something or make it better? Contact xcb@lists.freedesktop.org for corrections and improvements. They're accepting bestie applications π«Ά
And that's a wrap! This page came to you from the libxcb 1.17.0 era, stamped X Version 11, and it is so yours now. Go forth, pass conn, context_len, and context, and slay πβ¨ππ¦
π¦ 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