XCB_X_PRINT_PRINT_PUT_DOCUMENT_DATA_CHECKED(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_put_document_data ✨

okay bestie, come sit with me, we're reading a libxcb 1.17.0 man page from the X Version 11 era, section 3, and it's giving "the X Print extension has lore". This one's a Request function from xcb/xprint.h, and honestly? She's a void cookie girlie. Let's get into it. πŸ’…


🌸 NAME 🌸

xcb_x_print_print_put_document_data β€” and that's it, that's the whole name line, the original didn't even give us a description here. We move. 🫢


✨ SYNOPSIS ✨

First, you gotta let her in:

#include <xcb/xprint.h>

πŸŽ€ Request function πŸŽ€

xcb_void_cookie_t
xcb_x_print_print_put_document_data(xcb_connection_t *conn,
        xcb_drawable_t drawable, uint32_t len_data, uint16_t len_fmt,
        uint16_t len_options, const uint8_t *data,
        const xcb_x_print_string8_t *doc_format,
        const xcb_x_print_string8_t *options);

Look at all those parameters. She's high maintenance and we love her for it. πŸ’–


πŸ‘‘ REQUEST ARGUMENTS πŸ‘‘

  • conn β€” the XCB connection to X11. Your link to the mothership, your group chat with the server. 🌈
  • drawable β€” TODO: NOT YET DOCUMENTED. bestie I am so serious, that's literally what the page says. The docs said "not me leaving this blank" 😭
  • len_data β€” TODO: NOT YET DOCUMENTED. same energy, still blank, still iconic in a cursed way πŸ’€
  • len_fmt β€” TODO: NOT YET DOCUMENTED. the mystery continues, she's keeping secrets πŸ™ˆ
  • len_options β€” TODO: NOT YET DOCUMENTED. yes, another one. we're collecting them at this point πŸ“
  • data β€” TODO: NOT YET DOCUMENTED. still nothing, still slaying πŸ’…
  • doc_format β€” TODO: NOT YET DOCUMENTED. nope, not documented, no cap 🧚
  • options β€” TODO: NOT YET DOCUMENTED. and we close out the TODO list with a bang. periodt. ⭐
Not me pointing out that literally every single argument on this page is TODO: NOT YET DOCUMENTED. except conn. The XCB maintainers were busy, okay? They said "later." πŸ’œ

πŸ¦‹ DESCRIPTION πŸ¦‹

Completely empty. There is genuinely no description text in this man page. The heading exists, the vibes exist, the actual words do not. She's mysterious. She's minimal. She's giving main character who refuses to explain herself. ✨


πŸ’– RETURN VALUE πŸ’–

Returns an xcb_void_cookie_t. And here's the important part, bestie: errors (if any) have to be handled in the event loop. You don't get them handed to you right here. That's just how she operates. 😌

If you want to handle errors directly with xcb_request_check instead, use xcb_x_print_print_put_document_data_checked. See xcb-requests(3) for details. Two paths, pick your fighter. 🫢


πŸŽ€ ERRORS πŸŽ€

This request does never generate any errors.

no like, ever. zero. none. she is unbothered, moisturized, in her lane, focused, flourishing. πŸ§–β€β™€οΈβœ¨


🌈 SEE ALSO 🌈

Nothing listed. Empty. The section is there, standing in the doorway, with no references to hand you. πŸ¦‹


⭐ AUTHOR ⭐

Generated from xprint.xml. Contact xcb@lists.freedesktop.org for corrections and improvements.

(Translation: if you spot something wrong, the XCB girlies want your email. They're literally asking. Slide into that inbox. πŸ’Œ)


and that's the whole page, bestie β€” X Version 11, libxcb 1.17.0, a request that never errors, a void cookie, and an entire argument list that is one giant TODO. she's a legend, she's a mystery, she's thriving. mwah. πŸ’…πŸ’–πŸŽ€πŸ¦‹πŸŒΈ