xcb_selinux_g...perty_context(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_get_property_context(3) β€” XCB Requests πŸ’–

okay bestie, buckle up, we're reading a manpage together and it's giving libxcb energy. this one lives in the XCB Requests section, and yes the title is literally truncated in the wild like xcb_selinux_g...perty_context(3) because somebody let the column width win. we respect the chaos. 🫢


✨ NAME ✨

xcb_selinux_get_property_context β€”

not me telling you the description is literally blank in the source. that's not me being lazy, that's the manpage being mysterious. main character silence. πŸ’…

🌸 SYNOPSIS 🌸

first things first, you gotta pull in the header:

#include <xcb/xselinux.h>

πŸŽ€ Request function πŸŽ€

xcb_selinux_get_property_context_cookie_t
       xcb_selinux_get_property_context(xcb_connection_t *conn,
       xcb_window_t window, xcb_atom_t property);

πŸŽ€ Reply datastructure πŸŽ€

typedef struct xcb_selinux_get_property_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_context_reply_t;

look at those little pad0 and pad1[20] fields, they're just vibing, holding space, doing absolutely nothing. iconic behavior honestly. ✨

πŸŽ€ Reply function πŸŽ€

xcb_selinux_get_property_context_reply_t
       *xcb_selinux_get_property_context_reply(xcb_connection_t *conn,
       xcb_selinux_get_property_context_cookie_t cookie,
       xcb_generic_error_t **e);

πŸŽ€ Reply accessors πŸŽ€

these are the little helpers that get the good stuff out of the reply:

char *xcb_selinux_get_property_context_context(const
       xcb_selinux_get_property_context_request_t *reply);

int xcb_selinux_get_property_context_context_length(const
       xcb_selinux_get_property_context_reply_t *reply);

xcb_generic_iterator_t
       xcb_selinux_get_property_context_context_end(const
       xcb_selinux_get_property_context_reply_t *reply);

πŸ¦‹ REQUEST ARGUMENTS πŸ¦‹

  • conn β€” the XCB connection to X11. it's the line to the server, the group chat with the display, the whole reason we're here. πŸ’œ
  • window β€” TODO: NOT YET DOCUMENTED. yeah bestie, the docs just never got written. we move.
  • property β€” TODO: NOT YET DOCUMENTED. also a mystery. no cap.

🌈 REPLY FIELDS 🌈

  • response_type β€” the type of this reply, in this case XCB_SELINUX_GET_PROPERTY_CONTEXT. this field is also present in the xcb_generic_reply_t, and you can use it to tell replies apart from each other. it's the name tag at the party. πŸŽ€
  • sequence β€” the sequence number of the last request processed by the X11 server. it's how you know where you are in the timeline. ⭐
  • length β€” the length of the reply, in words. and reminder: a word is 4 bytes. not 2. not 8. four. πŸ’…
  • context_len β€” TODO: NOT YET DOCUMENTED. another gorgeous empty box. we love a mystery.

πŸ’« DESCRIPTION πŸ’«

so… there's a DESCRIPTION section. and it is empty. nothing. void. the silence is deafening. i'm not adding anything because that would be making stuff up and we don't do that here. πŸ™ˆ


πŸ‘‘ RETURN VALUE πŸ‘‘

it hands you back an xcb_selinux_get_property_context_cookie_t. cute lil cookie. πŸ“

and listen, errors? you don't get them here. you have to handle them when you call the reply function, xcb_selinux_get_property_context_reply.

if you'd rather handle your errors in the event loop instead, then use xcb_selinux_get_property_context_unchecked. see xcb-requests(3) for the details, bestie. 🫢


πŸ’€ ERRORS πŸ’€

this request does never generate any errors. zero. none. not a single one. slay, honestly.

🧚 SEE ALSO 🧚

…yeah there's a SEE ALSO heading and nothing under it. no references. no friends. just vibes. πŸ’œ


🌸 AUTHOR 🌸

Generated from xselinux.xml. Contact xcb@lists.freedesktop.org for corrections and improvements. go tell them if something's off, they're literally asking. πŸ“¬


okay that's the whole page!! and for the little sign-off moment: this beauty comes from X Version 11, libxcb 1.17.0, and the footer's manual name is xcb_selinux_g...perty_context(3). πŸ’–βœ¨πŸŽ€πŸ¦‹πŸŒΈπŸ’…πŸ«ΆπŸ˜­πŸ”₯πŸ‘‘πŸŒˆβ­πŸ’€πŸ™ˆπŸ“πŸ§šπŸ’œ

go forth and query your property context, bestie. periodt. πŸ’