xcb_x_print_print_end_page(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

✨ NAME ✨

xcb_x_print_print_end_page β€” bestie this is the one that ends a print page, and honestly the original page left the NAME line blank so we're all just vibing off the title here πŸ’–


🌸 SYNOPSIS 🌸

Grab the header first, always:

#include <xcb/xprint.h>

πŸŽ€ Request function

xcb_void_cookie_t xcb_x_print_print_end_page(xcb_connection_t *conn,
       uint8_t cancel);

πŸ¦‹ REQUEST ARGUMENTS πŸ¦‹

  • conn β€” your XCB connection to X11. the whole portal to the X server, no big deal πŸ’…
  • cancel β€” okay so. the original manpage literally says TODO: NOT YET DOCUMENTED. like girl we do not know 😭 it's a uint8_t, that's what we got, no cap.

πŸ’œ DESCRIPTION πŸ’œ

There is genuinely nothing here. The original page has an empty DESCRIPTION section. It's giving minimalism, it's giving "she said nothing and left" πŸ™ˆ so we move.


πŸ”₯ RETURN VALUE πŸ”₯

You get back an xcb_void_cookie_t. Errors (if any) have to be handled in the event loop β€” that's the assignment, bestie, handle them there.

If you'd rather handle errors directly with xcb_request_check, then use xcb_x_print_print_end_page_checked instead. See xcb-requests(3) for the details. iykyk 🫢


πŸ’€ ERRORS πŸ’€

This request does never generate any errors. zero. none. iconic behaviour honestly πŸ‘‘


🌈 SEE ALSO 🌈

Nothing listed. Empty section, empty plate, we eat nothing πŸ“


⭐ AUTHOR ⭐

Generated from xprint.xml. Contact xcb@lists.freedesktop.org for corrections and improvements β€” they're the ones who actually know things, fr fr.


okay that's the whole page, you ate that πŸ’… this was xcb_x_print_print_end_page(3) from X Version 11, libxcb 1.17.0 β€” go forth and end those pages, main character πŸŒΈβœ¨πŸŽ€