XCB_SELINUX_GET_PROPERTY_DATA_CONTEXT_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_data_context πŸ’–

okay bestie, welcome to the libxcb SELinux corner of the universe β€” this is the manual page for xcb_selinux_get_property_data_context from the XCB Requests fam, and yes we're gonna read the whole thing together, no skimming, no cap. πŸ¦‹


✨ NAME ✨

xcb_selinux_get_property_data_context β€” and that's literally all the NAME section says, bestie, it's giving mysterious main character energy πŸ™ˆ


✨ SYNOPSIS ✨

🌸 the include, obviously

#include <xcb/xselinux.h>

πŸ’… Request function

xcb_selinux_get_property_data_context_cookie_t
       xcb_selinux_get_property_data_context(xcb_connection_t *conn,
       xcb_window_t window, xcb_atom_t property);

πŸŽ€ Reply datastructure

typedef struct xcb_selinux_get_property_data_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_data_context_reply_t;

πŸ”₯ Reply function

xcb_selinux_get_property_data_context_reply_t
       *xcb_selinux_get_property_data_context_reply(xcb_connection_t *conn,
       xcb_selinux_get_property_data_context_cookie_t cookie,
       xcb_generic_error_t **e);

🫢 Reply accessors

char *xcb_selinux_get_property_data_context_context(const
       xcb_selinux_get_property_data_context_request_t *reply);

int xcb_selinux_get_property_data_context_context_length(const
       xcb_selinux_get_property_data_context_reply_t *reply);

xcb_generic_iterator_t
       xcb_selinux_get_property_data_context_context_end(const
       xcb_selinux_get_property_data_context_reply_t *reply);

✨ REQUEST ARGUMENTS ✨

  • conn β€” the XCB connection to X11. that's your whole link to the server, your ride-or-die, your situationship with the display. πŸ’œ
  • window β€” TODO: NOT YET DOCUMENTED. (the docs really said "we'll get back to you" 😭)
  • property β€” TODO: NOT YET DOCUMENTED. (same vibe, same void, fr fr πŸ’€)

✨ REPLY FIELDS ✨

  • response_type β€” the type of this reply, and in this case it's XCB_SELINUX_GET_PROPERTY_DATA_CONTEXT. this field also lives inside the xcb_generic_reply_t, so you can peek at it to tell your replies apart from each other β€” very "which one of y'all texted me" energy. πŸ‘‘
  • sequence β€” the sequence number of the last request processed by the X11 server. it's the receipts, bestie. 🧾✨
  • length β€” the length of the reply, in words (and a word is 4 bytes, periodt). 🌈
  • context_len β€” TODO: NOT YET DOCUMENTED. (again!! the mystery continues πŸ™ˆ)

✨ DESCRIPTION ✨

the DESCRIPTION section is empty, bestie. not a single word. it's giving silence, it's giving "let the synopsis speak for itself." iconic, honestly. πŸ’…


✨ RETURN VALUE ✨

It returns an xcb_selinux_get_property_data_context_cookie_t. πŸͺ

Errors have to be handled when you call the reply function xcb_selinux_get_property_data_context_reply.

If you'd rather handle errors in the event loop instead, use xcb_selinux_get_property_data_context_unchecked. See xcb-requests(3) for the details, bestie β€” it's the whole lore drop. πŸ“š


✨ ERRORS ✨

This request does never generate any errors. not one. zero. flawless behaviour, we love to see it. 😌✨


✨ SEE ALSO ✨

nothing here, bestie β€” the SEE ALSO section is empty. we're on our own out here. πŸ¦‹


✨ AUTHOR ✨

Generated from xselinux.xml. Contact xcb@lists.freedesktop.org for corrections and improvements. (yes, they really want your emails, go be a helper 🫢)


and that's the whole page, bestie!! you read all of it, I'm so proud, this is your main character moment. πŸŽ€

bye babe β€” this was X Version 11, libxcb 1.17.0, and it's been a pleasure doing Unix with you. slay, hydrate, and go read xcb-requests(3). mwah πŸ’–