xcb_res_query_clients(3)
π 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 caseXCB_RES_QUERY_CLIENTS. This field is also present in thexcb_generic_reply_tand 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 π
π¦ 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