xcb_res_query_clients(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_res_query_clients β€” the XCB glow-up

okay bestie, gather round, because this is xcb_res_query_clients(3) from the XCB Requests lineup and it's giving "I just want to know who's out here on the X server" energy. ✨


✨ NAME ✨

xcb_res_query_clients -

(yeah the description is literally empty, she's mysterious, we respect it πŸ’…)


🌸 SYNOPSIS 🌸

#include <xcb/res.h>

πŸŽ€ Request function

xcb_res_query_clients_cookie_t
       xcb_res_query_clients(xcb_connection_t *conn,

πŸ¦‹ Reply datastructure

typedef struct xcb_res_query_clients_reply_t {
    uint8_t  response_type;
    uint8_t  pad0;
    uint16_t sequence;
    uint32_t length;
    uint32_t num_clients;
    uint8_t  pad1[20];
} xcb_res_query_clients_reply_t;

🧚 Reply function

xcb_res_query_clients_reply_t
       *xcb_res_query_clients_reply(xcb_connection_t *conn,
       xcb_res_query_clients_cookie_t cookie, xcb_generic_error_t **e);

πŸ’œ Reply accessors

xcb_res_client_t *xcb_res_query_clients_clients(const
       xcb_res_query_clients_request_t *reply);

int xcb_res_query_clients_clients_length(const
       xcb_res_query_clients_reply_t *reply);

xcb_res_client_iterator_t xcb_res_query_clients_clients_iterator(const
       xcb_res_query_clients_reply_t *reply);

πŸ‘‘ REQUEST ARGUMENTS πŸ‘‘

  • conn β€” the XCB connection to X11, aka your little hotline to the server. πŸ“ž no connection, no vibes.

🌈 REPLY FIELDS 🌈

  • response_type β€” the type of this reply, in this case XCB_RES_QUERY_CLIENTS. This field is also present in the xcb_generic_reply_t and can be used to tell replies apart from each other. it's the little name tag so you know which reply just walked in πŸ’–
  • sequence β€” the sequence number of the last request processed by the X11 server. it's the server's "okay we got up to here" receipt ⭐
  • length β€” the length of the reply, in words (a word is 4 bytes). not wordle words bestie, 4-byte words 🫢
  • num_clients β€” TODO: NOT YET DOCUMENTED. yeah she's undocumented, we're all just out here living 😭

πŸ’€ DESCRIPTION πŸ’€

(empty. nothing. the void. she said "no notes" and meant it πŸ™ˆ)


πŸ”₯ RETURN VALUE πŸ”₯

Returns an xcb_res_query_clients_cookie_t. Errors have to be handled when calling the reply function xcb_res_query_clients_reply.

If you want to handle errors in the event loop instead, use xcb_res_query_clients_unchecked. See xcb-requests(3) for details.

so basically: you get a cookie now πŸͺ, and the actual answer comes later when you call the reply function. that's the whole async moment, no cap.

πŸ’… ERRORS πŸ’…

This request does never generate any errors.

periodt. zero errors. she's not like other requests ✨

🌟 SEE ALSO 🌟

(empty β€” she's self-sufficient, main character energy πŸ‘‘)


πŸŽ€ AUTHOR πŸŽ€

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


and that's the whole page bestie, iykyk πŸ’– go forth and query those clients, you absolute icon πŸ¦‹

sign-off time: this was X Version 11, libxcb 1.17.0, and yeah, xcb_res_query_clients(3) β€” mwah, obsessed πŸ’‹