xcb_lookup_color(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_lookup_color β€” XCB Requests πŸ’–

okay bestie, welcome to the manual page for xcb_lookup_color(3), a little gem from the XCB Requests collection πŸŽ€


✨ NAME ✨

xcb_lookup_color β€” and that's literally it, the description is a whole blank space in the original, so we're all just vibing with the mystery 🫢


✨ SYNOPSIS ✨

first up, the include, don't forget it or you'll be sad:

#include <xcb/xproto.h>

🌸 Request function 🌸

xcb_lookup_color_cookie_t xcb_lookup_color(xcb_connection_t *conn,
       xcb_colormap_t cmap, uint16_t name_len, const char *name);

🌸 Reply datastructure 🌸

typedef struct xcb_lookup_color_reply_t {
    uint8_t  response_type;
    uint8_t  pad0;
    uint16_t sequence;
    uint32_t length;
    uint16_t exact_red;
    uint16_t exact_green;
    uint16_t exact_blue;
    uint16_t visual_red;
    uint16_t visual_green;
    uint16_t visual_blue;
} xcb_lookup_color_reply_t;

🌸 Reply function 🌸

xcb_lookup_color_reply_t *xcb_lookup_color_reply(xcb_connection_t *conn,
       xcb_lookup_color_cookie_t cookie, xcb_generic_error_t **e);

✨ REQUEST ARGUMENTS ✨

  • conn β€” the XCB connection to X11 πŸ’… that's your whole link to the server, your main character connection, the one you can't skip.
  • cmap β€” TODO: NOT YET DOCUMENTED. yeah bestie the docs just said "not yet" πŸ™ˆ that's literally all we got.
  • name_len β€” TODO: NOT YET DOCUMENTED. same vibe, no tea to spill 😭
  • name β€” TODO: NOT YET DOCUMENTED. also a mystery box 🎁

✨ REPLY FIELDS ✨

  • response_type β€” the type of this reply, which in this case is XCB_LOOKUP_COLOR. this field is also hanging out in the xcb_generic_reply_t, and you can use it to tell replies apart from each other, like name tags at a party πŸŽ€
  • sequence β€” the sequence number of the last request that the X11 server processed πŸ”’
  • length β€” the length of the reply, in words (and a word is 4 bytes, no cap) ✨
  • exact_red β€” TODO: NOT YET DOCUMENTED. πŸ’€
  • exact_green β€” TODO: NOT YET DOCUMENTED. πŸ’€
  • exact_blue β€” TODO: NOT YET DOCUMENTED. πŸ’€
  • visual_red β€” TODO: NOT YET DOCUMENTED. πŸ’€
  • visual_green β€” TODO: NOT YET DOCUMENTED. πŸ’€
  • visual_blue β€” TODO: NOT YET DOCUMENTED. πŸ’€

✨ DESCRIPTION ✨

okay so… there is nothing here. the DESCRIPTION section is literally empty in the original. not a single word. it's giving silence, it's giving mystery, it's giving "we'll finish this later" πŸ¦‹


✨ RETURN VALUE ✨

it returns an xcb_lookup_color_cookie_t πŸͺ and errors have to be handled when you call the reply function xcb_lookup_color_reply.

if you'd rather handle errors in the event loop instead, use xcb_lookup_color_unchecked β€” and bestie, go read xcb-requests(3) for the details, it's got the lore πŸ‘‘


✨ ERRORS ✨

this request does never generate any errors. not one. zero. iconic behaviour, honestly. periodt πŸ’…

✨ SEE ALSO ✨

nothing. empty. a void. the original has no references here, so there's no extra reading to send you to 😭 go touch some grass instead 🌸


✨ AUTHOR ✨

generated from xproto.xml. contact xcb@lists.freedesktop.org for corrections and improvements πŸ’Œ


and that's the whole page, bestie!! this was served up by X Version 11, libxcb 1.17.0, and it's filed under xcb_lookup_color(3) β€” take care of her, she's doing her best πŸ’–βœ¨πŸŽ€πŸ¦‹