xcb_store_colors(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_store_colors — the XCB Requests girlies know 💖

okay so bestie, welcome to xcb_store_colors(3) from the XCB Requests manual. this one's short, but we're gonna make it iconic anyway. it's giving "mystery box" energy because honestly, the docs themselves are like... a work in progress. let's get into it 🎀

✨ NAME ✨

xcb_store_colors -

yeah bestie, that's it. that's the name section. it's literally just vibing there with a lil dash and no description. we move. 💅

🌸 SYNOPSIS 🌸

first things first, you gotta include the header:

#include <xcb/xproto.h>

🦋 Request function

xcb_void_cookie_t xcb_store_colors(xcb_connection_t *conn,
       xcb_colormap_t cmap, uint32_t items_len, const
       xcb_coloritem_t *items);

look at her go. so clean. so slay. ✨

👑 REQUEST ARGUMENTS 👑

  • conn — The XCB connection to X11. it's your lil phone line to the X server, the main character of the whole operation 🫶
  • items_len — TODO: NOT YET DOCUMENTED. yeah girl, nobody wrote it yet, i'm not gonna make something up, that's not the vibe 😭
  • cmap — TODO: NOT YET DOCUMENTED. same situation bestie, it's a mystery, we respect the mystery 🙈
  • items — TODO: NOT YET DOCUMENTED. yep. also undocumented. the lore is simply not there yet 💀
no cap: those TODO notes are straight from the source, so i'm keeping them exactly as-is. i'm not out here inventing behavior, that would be lying to my bestie and that's a crime 💜

🌈 DESCRIPTION 🌈

so... the description section is empty. like, genuinely empty. the original manpage just goes straight from the heading to the next one.

i know. i KNOW. we're all a little shook. but we keep it real around here, so: there is nothing here. that's the tea. 🍓

⭐ RETURN VALUE ⭐

it returns an xcb_void_cookie_t, bestie. that's the whole vibe.

and because it's a void cookie situation, any errors (if there even are any) have to be handled over in the event loop. that's just how we do it.

but WAIT — if you'd rather handle errors directly, there's a whole other path:

  • if you want to handle errors directly with xcb_request_check instead, use xcb_store_colors_checked 💅
  • and go peek at xcb-requests(3) for all the deets

💀 ERRORS 💀

this request does never generate any errors.

iconic behavior honestly. zero drama. no error codes, no nonsense, just peace and quiet 🌸✨

🎀 SEE ALSO 🎀

nothing here either bestie. the section exists but it's empty. i'm not gonna fill it with guesses because that's not the assignment. periodt.

💜 AUTHOR 💜

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

so if something's wrong or you wanna improve it, that's the address. the girlies who made this are reachable. 🫶

and that's the whole page, bestie!! no cap, you now know literally everything this manpage contains 💖✨

this lil tour was brought to you by X Version 11 and libxcb 1.17.0 🦋 mwah, go handle your event loop, you ate 👑

📦 where this page comes from