XCB_SELINUX_GET_PROPERTY_CREATE_CONTEXT_CONTEXT(3)
πΈ NAME πΈ
xcb_selinux_get_property_create_context β bestie, that's the whole name, the description slot is literally empty, it's giving mystery β¨
π SYNOPSIS π
First things first, you gotta pull in the header:
#include <xcb/xselinux.h>
π Request function π
xcb_selinux_get_property_create_context_cookie_t
xcb_selinux_get_property_create_context(xcb_connection_t *conn,
π¦ Reply datastructure π¦
typedef struct xcb_selinux_get_property_create_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_property_create_context_reply_t;
β¨ Reply function β¨
xcb_selinux_get_property_create_context_reply_t
*xcb_selinux_get_property_create_context_reply(xcb_connection_t *conn,
xcb_selinux_get_property_create_context_cookie_t cookie,
xcb_generic_error_t **e);
π Reply accessors π
char *xcb_selinux_get_property_create_context_context(const
xcb_selinux_get_property_create_context_request_t *reply);
int xcb_selinux_get_property_create_context_context_length(const
xcb_selinux_get_property_create_context_reply_t *reply);
xcb_generic_iterator_t
xcb_selinux_get_property_create_context_context_end(const
xcb_selinux_get_property_create_context_reply_t *reply);
π REQUEST ARGUMENTS π
connβ the XCB connection to X11. That's it, that's the whole argument list, she's low maintenance π
π REPLY FIELDS π
response_typeβ the type of this reply, and in this case it'sXCB_SELINUX_GET_PROPERTY_CREATE_CONTEXT. This field is also chillin' in thexcb_generic_reply_t, so you can use it to tell replies apart from each other when they're all up in your queue πsequenceβ the sequence number of the last request the X11 server processed. It's like a lil receipt number fr fr π§Ύlengthβ how long the reply is, measured in words (and a word is 4 bytes, no cap) πcontext_lenβ TODO: NOT YET DOCUMENTED. Yeah bestie, they left us on read with this one π
π DESCRIPTION π
So um. There's a DESCRIPTION heading. And under it? Nothing. Absolutely nothing. An empty section, a blank page, the silence is deafening π The documentation said "not me today" and logged off.
β RETURN VALUE β
You get back an xcb_selinux_get_property_create_context_cookie_t, periodt πͺ
Errors have to be handled when you call the reply function, xcb_selinux_get_property_create_context_reply.
But wait β if you'd rather handle errors in the event loop instead, use xcb_selinux_get_property_create_context_unchecked. Peep xcb-requests(3) for all the deets, iykyk π
π₯ ERRORS π₯
This request does never generate any errors. Zero. None. She's unbothered, moisturized, in her lane, thriving π β¨
π«Ά SEE ALSO π«Ά
Nothing here either bestie, the see-also slot is giving empty inbox energy π
π AUTHOR π
Generated from xselinux.xml. If you spot something sus, contact xcb@lists.freedesktop.org for corrections and improvements β they actually want the feedback, fr fr π«Ά
And that's the whole page, babe β from X Version 11 era, libxcb 1.17.0 energy. Go forth and get that property create context, you absolute main character ππΈπ
π¦ 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