xcb_create_colormap(3)

💖 xcb_create_colormap — bestie's guide to the XCB requests manual 💖

okay so this is xcb_create_colormap(3) from the XCB Requests crew — the whole manpage, no skips, no cap. it's giving "short but mysterious" and honestly? we're gonna walk through every single crumb. ✨

---

✨ NAME ✨

xcb_create_colormap — and that's it, bestie 😭 the description slot is literally empty in the source. no tagline, no subtitle, no nothing. main character energy with zero intro. iconic behavior.

---

✨ SYNOPSIS ✨

first things first, you gotta bring in the header:

#include <xcb/xproto.h>

🎀 Request function 🎀

and here's the function itself — look at her:

xcb_void_cookie_t xcb_create_colormap(xcb_connection_t *conn,
       uint8_t alloc, xcb_colormap_t mid, xcb_window_t window,
       xcb_visualid_t visual);

yes she returns an xcb_void_cookie_t. yes she's void. we love a queen who gives you a cookie and no actual value 💅

---

✨ REQUEST ARGUMENTS ✨

let's go through every single one, no skipping, periodt:

• conn — your XCB connection to X11. the whole lifeline, the situationship you can't escape. 🫶
• alloc — one of the following values, and there are exactly two:
  • XCB_COLORMAP_ALLOC_NONE — TODO: NOT YET DOCUMENTED. yeah. that's the whole thing. the docs said "we'll get to it" and then never did 🙈
  • XCB_COLORMAP_ALLOC_ALL — TODO: NOT YET DOCUMENTED. also TODO: NOT YET DOCUMENTED. — and listen, there's a second TODO: NOT YET DOCUMENTED. just hanging out after it in the original, unclaimed, unexplained. two whole TODOs. the mystery is not solving itself, bestie 😭
• mid — TODO: NOT YET DOCUMENTED. the placeholder is placeholdering.
• window — TODO: NOT YET DOCUMENTED. same vibe, different argument.
• visual — TODO: NOT YET DOCUMENTED. and that's the last one, all equally undocumented.

---

✨ DESCRIPTION ✨

nothing. empty. blank. this section has no text in it at all. the void is voiding. we respect her privacy 💖

---

✨ RETURN VALUE ✨

okay here's actual info, lock in 🔥

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_create_colormap_checked. See xcb-requests(3) for details.

so basically: cookie now, consequences later. either you catch your errors in the event loop, or you go the xcb_request_check route with xcb_create_colormap_checked. your choice, your journey, slay ✨

---

✨ ERRORS ✨

This request does never generate any errors.

read it again. never. zero. none. she is unproblematic in the error department, and honestly? that's the dream 🌸

---

✨ SEE ALSO ✨

empty. nothing here. no cross-references, no friends, no neighbors. she stands alone 🦋

---

✨ AUTHOR ✨

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

like, if you spot something wrong, that's the email. they want your feedback, fr fr 💌

---

and that's the whole page, bestie — every option, every argument, every single TODO: NOT YET DOCUMENTED., every section, all of it. we ate and left no crumbs 👑

cute little sign-off: this one's from X Version 11, libxcb 1.17.0, and the manpage date stamped alongside it. mwah 💅🎀