xcb_lookup_color(3)
π 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 isXCB_LOOKUP_COLOR. this field is also hanging out in thexcb_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 πβ¨ππ¦
π¦ 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