XCB_X_PRINT_PRINT_GET_SCREEN_OF_CONTEXT_UNCHECKED(3)
π xcb_x_print_print_get_screen_of_context π
okay bestie, welcome to the XCB Requests section 3 era of your life π this one lives in xcb/xprint.h and it's giving "ask the X server which screen this print context is on" energy. no cap.
β¨ NAME β¨
xcb_x_print_print_get_screen_of_context β literally no description in the original, it just vibes there being mysterious π
πΈ SYNOPSIS πΈ
#include <xcb/xprint.h>
π¦ Request function
xcb_x_print_print_get_screen_of_context_cookie_t
xcb_x_print_print_get_screen_of_context(xcb_connection_t *conn,
π§ Reply datastructure
typedef struct xcb_x_print_print_get_screen_of_context_reply_t {
uint8_t response_type;
uint8_t pad0;
uint16_t sequence;
uint32_t length;
xcb_window_t root;
} xcb_x_print_print_get_screen_of_context_reply_t;
π« Reply function
xcb_x_print_print_get_screen_of_context_reply_t
*xcb_x_print_print_get_screen_of_context_reply(xcb_connection_t *conn,
xcb_x_print_print_get_screen_of_context_cookie_t cookie,
xcb_generic_error_t **e);
π«Ά REQUEST ARGUMENTS π«Ά
connβ your XCB connection to X11, the main character of every single one of these functions fr fr π
π REPLY FIELDS π
response_typeβ the type of this reply, which in this case isXCB_X_PRINT_PRINT_GET_SCREEN_OF_CONTEXT. this field is also hanging out in thexcb_generic_reply_t, so you can use it to tell your replies apart from each other when they're all piled up in the group chat β¨sequenceβ the sequence number of the last request the X11 server actually processed π’lengthβ the length of the reply, measured in words. and yes bestie, a word here is 4 bytes, that's just the lore πrootβTODO: NOT YET DOCUMENTED.the original literally says this, we're not making it up π
π DESCRIPTION π
okay so. there is no description. the original left this section completely blank. it's giving "the void stared back". we respect the silence π
β RETURN VALUE β
Returns an xcb_x_print_print_get_screen_of_context_cookie_t πͺ (yes, a cookie, iconic behavior).
Errors have to be handled when you call the reply function xcb_x_print_print_get_screen_of_context_reply.
If you'd rather handle errors in the event loop instead, use xcb_x_print_print_get_screen_of_context_unchecked. See xcb-requests(3) for the details, bestie, it's all in there π
π ERRORS π
This request does never generate any errors. not one. zero. slay. periodt. π β¨
π SEE ALSO π
nothing here either. the original lists no references. empty. a whole vibe. π¦
π AUTHOR π
Generated from xprint.xml. Contact xcb@lists.freedesktop.org for corrections and improvements π§
and that's the whole page, bestie!! X Version 11, libxcb 1.17.0, mwah π go forth and get that screen of context, i believe in you π«Άβ¨
π¦ 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