XCB_SELINUX_GET_PROPERTY_CREATE_CONTEXT_CONTEXT_END(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

🌸 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's XCB_SELINUX_GET_PROPERTY_CREATE_CONTEXT. This field is also chillin' in the xcb_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 πŸ‘‘πŸŒΈπŸ’–