XCB_X_PRINT_PRINT_DESTROY_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_x_print_print_destroy_context πŸ’–

okay bestie, so this is a page from the XCB Requests family β€” it's the libxcb manual for xcb_x_print_print_destroy_context(3), straight out of the X Version 11 / libxcb world. buckle up, it's a short one but we're gonna make it cute. πŸŽ€


✨ NAME ✨

xcb_x_print_print_destroy_context β€” (yeah the name field is literally empty in the original, the function name is doing all the heavy lifting here, iconic of it tbh)


🌸 SYNOPSIS 🌸

first things first, you gotta pull in the header:

#include <xcb/xprint.h>

Request function

xcb_void_cookie_t
xcb_x_print_print_destroy_context(xcb_connection_t *conn,
                                  uint32_t context);

like. that's it. that's the whole function. she's simple, she's a void cookie, she's giving low maintenance. πŸ’…


πŸ¦‹ REQUEST ARGUMENTS πŸ¦‹

  • conn β€” the XCB connection to X11. your link to the mothership, your group chat with the X server. no conn, no vibes.
  • context β€” TODO: NOT YET DOCUMENTED. yeah bestie, they really just left us on read with that one. no cap, the docs said "not yet documented" and then closed the laptop. πŸ™ˆ

πŸ’€ DESCRIPTION πŸ’€

...it's empty. genuinely, completely, 100% empty in the original. not a single word. the description section is giving mystery, giving enigmatic main character, giving we ran out of time before the release. the silence is loud, fr fr. 😭


πŸ”₯ RETURN VALUE πŸ”₯

she returns an xcb_void_cookie_t. because that's what void requests do β€” they hand you a cookie and ✨nothing else✨.

errors (if any, and here there are none, see below πŸ‘€) have to be handled in the event loop. that's the deal. that's the assignment.

if you're the kind of person who wants to handle errors directly instead of doing the whole event loop dance, you use xcb_request_check β€” and in that case, use xcb_x_print_print_destroy_context_checked instead. see xcb-requests(3) for all the details, she explains the cookie/checked situation way better than I can. πŸ“


πŸ‘‘ ERRORS πŸ‘‘

this request never generates any errors. zero. none. zilch. the vibe check is immaculate, she simply cannot fail. 🌈


🧚 SEE ALSO 🧚

bestie... it's blank. the SEE ALSO section sees no one. the cross-references ghosted us. πŸ’”

πŸ’œ AUTHOR πŸ’œ

Generated from xprint.xml. if you've got corrections and improvements, hit up xcb@lists.freedesktop.org β€” they're the ones who can fix it, not me, I'm just the messenger with good taste. 🫢


and that's the whole page, babes. ✨ this came to you from X Version 11, rocking libxcb 1.17.0 β€” a real classic, a legend, an icon. mwah. πŸ’–πŸŽ€πŸ¦‹