xcb_x_print_print_start_doc(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_x_print_print_start_doc β€” the XCB Requests girlies' guide πŸ’–

okay so bestie, we're in the XCB Requests section of the manual and today's main character is xcb_x_print_print_start_doc. no cap, that's the whole vibe. let's get into it 🫢


✨ NAME ✨

xcb_x_print_print_start_doc β€” literally just the name, that's it. the original page didn't give us a one-liner description either, so we're all just out here living our truth πŸ’…


✨ SYNOPSIS ✨

first things first, you gotta pull in the header:

#include <xcb/xprint.h>

🌸 Request function 🌸

xcb_void_cookie_t xcb_x_print_print_start_doc(xcb_connection_t *conn,
       uint8_t driver_mode);

look at her. two args, one cookie, zero notes. iconic behavior honestly πŸŽ€


✨ REQUEST ARGUMENTS ✨

  • conn β€” your XCB connection to X11. the whole group chat with the X server, basically πŸ¦‹
  • driver_mode β€” and here's where the plot twist is: this one is TODO: NOT YET DOCUMENTED. not me being lazy, that's genuinely what the manual says. the lore is simply not written down yet 😭 so like, don't ask me what to pass, ask the XCB girlies.

✨ DESCRIPTION ✨

okay so. and i cannot stress this enough. there is nothing here. the DESCRIPTION section is empty in the original. not a single sentence. zero. void. she's giving mystery, she's giving silence, she's giving xcb_void_cookie_t energy πŸ’€


✨ RETURN VALUE ✨

she returns an xcb_void_cookie_t. that's your lil receipt bestie 🧾 and here's the tea: any errors (if there even are any) have to be handled in the event loop. like, you don't just get them handed to you, you gotta go collect them.

if you'd rather handle errors directly with xcb_request_check instead, then use xcb_x_print_print_start_doc_checked. different function, different vibe, same request.

for all the deets on that, go read xcb-requests(3). it's the required reading, fr fr πŸ“š


✨ ERRORS ✨

This request does never generate any errors. 😌✨

not one. she's flawless. no drama, no errors, no notes. periodt πŸ‘‘


✨ SEE ALSO ✨

...and that's the section. empty. nothing listed. the "see also" girlies did not show up today πŸ™ˆ


✨ AUTHOR ✨

this whole thing was Generated from xprint.xml. if you've got corrections or improvements, hit up xcb@lists.freedesktop.org β€” they're the ones who actually take the feedback πŸ’œ


and that's the page!! πŸŽ€ before i go, a lil sign-off for the record books: this is X Version 11, running libxcb 1.17.0, filed under xcb_x_print_print_start_doc(3). slay, stay hydrated, and always handle your errors in the event loop bestie πŸŒˆπŸ’–πŸ¦‹