xcb_copy_colormap_and_free(3)
π xcb_copy_colormap_and_free
okay bestie, welcome to the β¨ xcb_copy_colormap_and_free β¨ page β it's part of XCB Requests, and ngl she's a little mysterious because half this page is still a TODO π. But we're gonna walk through it together, no cap.
πΈ NAME πΈ
okay so the NAME section here is literally empty? Like, blank. Nothing. The manpage never filled in a one-line description, so there's no cute summary tagline for this one. It's giving "mystery icon" π. Just know the whole page is about xcb_copy_colormap_and_free, and that's the vibe.
β¨ SYNOPSIS β¨
First up, you gotta pull in the header:
#include <xcb/xproto.h>
π Request function π
And here's the actual request function signature, character for character:
xcb_void_cookie_t xcb_copy_colormap_and_free(xcb_connection_t *conn,
xcb_colormap_t mid, xcb_colormap_t src_cmap);
π¦ REQUEST ARGUMENTS π¦
connβ the XCB connection to X11. Your lil hotline to the server, fr fr π .midβ TODO: NOT YET DOCUMENTED. yeah... the docs just never said. We don't invent lore here, so this is all we got π.src_cmapβ TODO: NOT YET DOCUMENTED. same situation bestie, the manpage left it blank π.
π DESCRIPTION π
So the DESCRIPTION section? Completely empty. No prose, no explanation, nothing. The page just moves right along. We are NOT making stuff up to fill it in β that's the rule π. If you need the tea on what this request actually does, it's not on this page.
π RETURN VALUE π
She returns an xcb_void_cookie_t. And because that's a void cookie, any errors (if there even are any) have to be handled over in the event loop, not right here.
If you'd rather handle errors directly with xcb_request_check instead, then you want the checked version: xcb_copy_colormap_and_free_checked. See xcb-requests(3) for all the deets on how that whole thing works π«Ά.
π₯ ERRORS π₯
Good news era: this request does never generate any errors. Zero. None. Not a single one. Slay π β¨
β SEE ALSO β
Nothing listed here! The SEE ALSO section is empty, so there's no cross-reference posse to send you to. (The only page it nods at in the prose above is xcb-requests(3), for the request-handling details.)
π AUTHOR π
Generated from xproto.xml. If you've got corrections or improvements, hmu at xcb@lists.freedesktop.org β they're literally asking for the fixes, bestie π.
and that's the whole page!! π¦ thank you for coming to my ted talk. this one came from X Version 11, libxcb 1.17.0, and it's the xcb_copy_colormap_and_free(3) page itself. go forth and be iconic πΈπβ¨
π¦ where this page comes from
- alpine 3.22: libxcb-doc 1.17.0-r0 Β· MIT
- alpine 3.23: libxcb-doc 1.17.0-r1 Β· MIT
- alpine 3.24: libxcb-doc 1.17.0-r2 Β· MIT
- arch rolling: libxcb 1.17.0-1 Β· X11
- centos-stream 10: libxcb-devel 1.17.0-3.el10 Β· X11
- debian trixie: libxcb-doc 1.17.0-2
- fedora 43: libxcb-devel 1.17.0-6.fc43 Β· X11
- fedora 43: libxcb-devel 1.17.0-6.fc43 Β· X11
- fedora 44: libxcb-devel 1.17.0-7.fc44 Β· X11
- fedora 44: libxcb-devel 1.17.0-7.fc44 Β· X11
- nixpkgs unstable: libxcb 1.17.0
- opensuse-leap 16.0: libxcb-devel-doc 1.17.0-160000.2.2 Β· MIT
- ubuntu questing: libxcb-doc 1.17.0-2build1
- ubuntu resolute: libxcb-doc 1.17.0-2ubuntu1
- ubuntu stonking: libxcb-doc 1.17.0-2ubuntu1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms