xcb_composite...window_pixmap(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_composite...window_pixmap(3) 💖

okay bestie, sit down, hydrate, because we're reading the XCB Requests manual page for xcb_composite_name_window_pixmap, and honestly? it's giving "short but iconic." no cap, this page is like four facts long and three of them are basically shrugs. we stan a minimal queen. 🎀

✨ NAME ✨

xcb_composite_name_window_pixmap —

and that's it. that trailing dash? nothing after it. the one-line summary is literally empty, like my calendar on a friday night. 💀 nobody ever wrote the little tagline, so we move on, bestie, we don't dwell.

🌸 SYNOPSIS 🌸

first you gotta pull in the header, fr fr:

#include <xcb/composite.h>

🦋 Request function 🦋

and here's the function itself, character for character, no edits, periodt:

xcb_void_cookie_t
       xcb_composite_name_window_pixmap(xcb_connection_t *conn,
       xcb_window_t window, xcb_pixmap_t pixmap);

🎀 REQUEST ARGUMENTS 🎀

three lil arguments walk into a bar. here's the rundown:

  • conn — the XCB connection to X11. that's your link to the server, your main character connection, the whole vibe. 🔥
  • window — the manual says, and I quote: TODO: NOT YET DOCUMENTED. so yeah. it's giving "we'll finish this later" and later never came. 🙈
  • pixmap — also TODO: NOT YET DOCUMENTED. same energy, same unfinished homework, same iconic negligence. 😭
not me reading two arguments in a row that both say TODO: NOT YET DOCUMENTED. the way this page said "figure it out yourself" twice and then dipped 💅

💜 DESCRIPTION 💜

okay so. the DESCRIPTION section on this page is… empty. nothing. void. a blank little space where prose should live. so there is genuinely nothing to tell you here — I'm not gonna make something up because that would be fake of me. it's just silence, bestie. peaceful, honestly. 🧚

⭐ RETURN VALUE ⭐

here's the real tea, and this part IS documented:

Returns an xcb_void_cookie_t. and if there are any errors? you gotta handle them in the event loop, okay? that's on you, not on the function.

but wait — if you'd rather deal with errors directly, using xcb_request_check instead, then use xcb_composite_name_window_pixmap_checked instead. see xcb-requests(3) for the details. 🔍

🌈 ERRORS 🌈

good news, bestie: this request does never generate any errors.

like, zero. none. not a single one. it simply does not have that in it. she's unproblematic. she's drama-free. she ate and left no crumbs. 👑

💅 SEE ALSO 💅

nothing listed here. nope, not a single cross-reference, not even one. the section exists purely for the aesthetic. iconic behavior, honestly. 🫶

📜 AUTHOR 📜

Generated from composite.xml. and if you spot something wrong, or you want to send improvements, hit up xcb@lists.freedesktop.org — they take corrections and improvements, so slide into those inboxes politely. 💌

okay and that's the whole page, we made it, we're free!! 🦋✨ this was X Version 11, libxcb 1.17.0, and you read the entire thing top to bottom like a scholar. so proud of you. go drink some water, log off, and remember: TODO: NOT YET DOCUMENTED. is a mood, but it is not a personality. bye bestie!! 💖🎀🌟

📦 where this page comes from