xcb_list_installed_colormaps(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_list_installed_colormaps πŸ’…

okay bestie, so this is a page from XCB Requests, the xcb_list_installed_colormaps(3) one, and it's giving "short but iconic". Let me tell you everything, no cap, every single detail intact. πŸŽ€


✨ NAME ✨

xcb_list_installed_colormaps β€” literally just that. The NAME section is serving empty-plate energy, no description attached. We move. πŸ’€


πŸ¦‹ SYNOPSIS πŸ¦‹

First thing, you gotta include the header:

#include <xcb/xproto.h>

🌸 Request function 🌸

xcb_list_installed_colormaps_cookie_t
       xcb_list_installed_colormaps(xcb_connection_t *conn,
       xcb_window_t window);

πŸ’– Reply datastructure πŸ’–

typedef struct xcb_list_installed_colormaps_reply_t {
    uint8_t  response_type;
    uint8_t  pad0;
    uint16_t sequence;
    uint32_t length;
    uint16_t cmaps_len;
    uint8_t  pad1[22];
} xcb_list_installed_colormaps_reply_t;

✨ Reply function ✨

xcb_list_installed_colormaps_reply_t
       *xcb_list_installed_colormaps_reply(xcb_connection_t *conn,
       xcb_list_installed_colormaps_cookie_t cookie,
       xcb_generic_error_t **e);

πŸŽ€ Reply accessors πŸŽ€

xcb_colormap_t *xcb_list_installed_colormaps_cmaps(const
       xcb_list_installed_colormaps_request_t *reply);

int xcb_list_installed_colormaps_cmaps_length(const
       xcb_list_installed_colormaps_reply_t *reply);

xcb_generic_iterator_t xcb_list_installed_colormaps_cmaps_end(const
       xcb_list_installed_colormaps_reply_t *reply);

πŸ‘‘ REQUEST ARGUMENTS πŸ‘‘

  • conn β€” the XCB connection to X11. your little hotline to the server, periodt. 🫢
  • window β€” TODO: NOT YET DOCUMENTED. bestie the docs simply did not show up. no further info, and I'm not about to make any up. πŸ™ˆ

πŸ’œ REPLY FIELDS πŸ’œ

  • response_type β€” the type of this reply, and in this case it's XCB_LIST_INSTALLED_COLORMAPS. This field is also chilling inside the xcb_generic_reply_t, so you can use it to tell replies apart from each other. it's the name tag at the party. πŸŽ€
  • sequence β€” the sequence number of the last request processed by the X11 server. the receipts, basically. 🧾
  • length β€” the length of the reply, in words (and a word is 4 bytes, iykyk). ⭐
  • cmaps_len β€” TODO: NOT YET DOCUMENTED. again, the docs ghosted us. no invented lore here. πŸ’€

🌈 DESCRIPTION 🌈

this section is empty in the original. like, completely. nothing to see, nothing to report, we're not filling it in with fanfic. πŸ’…

πŸ”₯ RETURN VALUE πŸ”₯

Returns an xcb_list_installed_colormaps_cookie_t. Errors have to be handled when you call the reply function, xcb_list_installed_colormaps_reply. That's the deal, bestie. ✨

If you'd rather handle errors in the event loop instead, use xcb_list_installed_colormaps_unchecked. See xcb-requests(3) for details. 🫢


πŸ’€ ERRORS πŸ’€

This request does never generate any errors. not one. zero. the calmest request in the group chat. 😭


πŸ¦‹ SEE ALSO πŸ¦‹

nothing listed here in the original β€” just vibes and an empty section. πŸ‘‘

🌸 AUTHOR 🌸

Generated from xproto.xml. Contact xcb@lists.freedesktop.org for corrections and improvements. they're literally so sweet for that. πŸ’–


and that's the whole page, bestie β€” brought to you by X Version 11, libxcb 1.17.0, and the date stamped on the original footer. slay, go install some colormaps, ily. πŸ’…βœ¨πŸŒˆ