XCB_X_PRINT_PRINT_GET_DOCUMENT_DATA_UNCHECKED(3)
β¨ NAME β¨
xcb_x_print_print_get_document_data β bestie, this is one of those libxcb X Print request pages where the docs literally say nothing else, and I'm not gonna lie to you about that π
πΈ SYNOPSIS πΈ
Pull in the header first, always:
#include <xcb/xprint.h>
π Request function
xcb_x_print_print_get_document_data_cookie_t
xcb_x_print_print_get_document_data(xcb_connection_t *conn,
xcb_x_print_pcontext_t context, uint32_t max_bytes);
π¦ Reply datastructure
typedef struct xcb_x_print_print_get_document_data_reply_t {
uint8_t response_type;
uint8_t pad0;
uint16_t sequence;
uint32_t length;
uint32_t status_code;
uint32_t finished_flag;
uint32_t dataLen;
uint8_t pad1[12];
} xcb_x_print_print_get_document_data_reply_t;
π Reply function
xcb_x_print_print_get_document_data_reply_t
*xcb_x_print_print_get_document_data_reply(xcb_connection_t *conn,
xcb_x_print_print_get_document_data_cookie_t cookie,
xcb_generic_error_t **e);
π Reply accessors
uint8_t *xcb_x_print_print_get_document_data_data(const
xcb_x_print_print_get_document_data_request_t *reply);
int xcb_x_print_print_get_document_data_data_length(const
xcb_x_print_print_get_document_data_reply_t *reply);
xcb_generic_iterator_t
xcb_x_print_print_get_document_data_data_end(const
xcb_x_print_print_get_document_data_reply_t *reply);
π REQUEST ARGUMENTS π
connβ the XCB connection to X11. Your lil phone line to the server, basically π«ΆcontextβTODO: NOT YET DOCUMENTED.yeah. that's it. that's the whole description. iconic of them honestly πmax_bytesβTODO: NOT YET DOCUMENTED.same energy, same silence π
π REPLY FIELDS π
response_typeβ the type of this reply, and for this one it'sXCB_X_PRINT_PRINT_GET_DOCUMENT_DATA. This field also lives in thexcb_generic_reply_t, so you can use it to tell your replies apart from each other. Very "which one of y'all is this" energy β¨sequenceβ the sequence number of the last request processed by the X11 server. Receipts, but for the server π§Ύlengthβ how long the reply is, in words (and a word here is 4 bytes, keep up bestie) πstatus_codeβTODO: NOT YET DOCUMENTED.πfinished_flagβTODO: NOT YET DOCUMENTED.πdataLenβTODO: NOT YET DOCUMENTED.lowkey a mystery, highkey still a real field π
π« DESCRIPTION π«
Okay so... there is genuinely nothing here. The DESCRIPTION section is empty. Not a single word. The void. The silence. We move π¦
β RETURN VALUE β
Returns an xcb_x_print_print_get_document_data_cookie_t. Real talk: errors have to be handled when you call the reply function xcb_x_print_print_get_document_data_reply.
If you'd rather handle errors in the event loop instead, use xcb_x_print_print_get_document_data_unchecked. Peep xcb-requests(3) for the details, no cap π
π ERRORS π
This request does never generate any errors. Not one. Zero. None. She's unproblematic, periodt π
π₯ SEE ALSO π₯
(blank. nothing. an empty shelf. we love a minimalist moment πΈ)
π AUTHOR π
Generated from xprint.xml. Contact xcb@lists.freedesktop.org for corrections and improvements β they're literally asking for your notes, bestie, so don't be shy π«Ά
X Version 11 Β· libxcb 1.17.0 β that's the whole vibe check, the source and the version, and I'm signing off like the main character I am. mwah πβ¨
π¦ 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