xcb_x_print_p...et_attributes(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_p...et_attributes — the XCB Requests one, bestie

okay so this is a page from the XCB Requests manual set, and the star of the show is xcb_x_print_print_set_attributes ✨ (yes the title is all squished with ... in it, that's just how the man page file is named, don't worry about it 🫶).

🌸 NAME 🌸

xcb_x_print_print_set_attributes —

literally nothing else. the description is empty. it's giving mystery. it's giving figure it out yourself, babe. 💀

✨ SYNOPSIS ✨

First, you gotta bring in the header:

#include <xcb/xprint.h>

🎀 Request function 🎀

xcb_void_cookie_t
       xcb_x_print_print_set_attributes(xcb_connection_t *conn,
       xcb_x_print_pcontext_t context, uint32_t stringLen, uint8_t pool,
       uint8_t rule, uint32_t attributes_len, const
       xcb_x_print_string8_t *attributes);

she's long. she's got seven whole arguments. she ate and left no crumbs 👑

🦋 REQUEST ARGUMENTS 🦋

  • conn — The XCB connection to X11. your lil link to the X server, the group chat you're texting into 💬
  • context — TODO: NOT YET DOCUMENTED. yeah bestie, the docs just did not show up to class that day 🙈
  • stringLen — TODO: NOT YET DOCUMENTED.
  • pool — TODO: NOT YET DOCUMENTED.
  • rule — TODO: NOT YET DOCUMENTED.
  • attributes_len — TODO: NOT YET DOCUMENTED.
  • attributes — TODO: NOT YET DOCUMENTED.
not me reading a whole man page where half the arguments are literally "TODO: NOT YET DOCUMENTED" 😭 the xprint corner of X11 is out here with main character energy and zero lore. we love an enigma tho. 🧚

🌈 DESCRIPTION 🌈

...it's empty. like, genuinely. there is no description section content. the description is a void. a cute lil void. ⭐

💖 RETURN VALUE 💖

Returns an xcb_void_cookie_t. Errors (if any) have to be handled in the event loop.

If you want to handle errors directly with xcb_request_check instead, use xcb_x_print_print_set_attributes_checked. See xcb-requests(3) for details.

so basically: cookie now, feelings later. you go catch those errors in the event loop, or you grab the _checked version and deal with it on the spot. no cap. 🍓

🔥 ERRORS 🔥

This request does never generate any errors.

she's flawless. she's unbothered. she has never once been problematic. iconic behaviour honestly 👑

👑 SEE ALSO 👑

(empty. nothing to see here. move along, bestie 💅)

💜 AUTHOR 💜

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

and that's the whole vibe check 🫶 this was X Version 11, libxcb 1.17.0 — slay, mwah, drink water, and may your cookies always be void ✨💖🎀

📦 where this page comes from