xcb_sync_list_system_counters(3)
β¨ xcb_sync_list_system_counters(3) β¨
okay bestie, pull up a chair, because we're looking at xcb_sync_list_system_counters(3) from the libxcb crew π
this one lives in the SYNC extension part of XCB and it's giving "let me see your system counters" energy.
πΈ NAME πΈ
xcb_sync_list_system_counters β
not gonna lie, the description slot in the original is literally empty. zero words. a vibe, honestly. so we work with what we have π«Ά
π SYNOPSIS π
#include <xcb/sync.h>
π Request function
xcb_sync_list_system_counters_cookie_t
xcb_sync_list_system_counters(xcb_connection_t *conn,
π¦ Reply datastructure
typedef struct xcb_sync_list_system_counters_reply_t {
uint8_t response_type;
uint8_t pad0;
uint16_t sequence;
uint32_t length;
uint32_t counters_len;
uint8_t pad1[20];
} xcb_sync_list_system_counters_reply_t;
π§ Reply function
xcb_sync_list_system_counters_reply_t
*xcb_sync_list_system_counters_reply(xcb_connection_t *conn,
xcb_sync_list_system_counters_cookie_t cookie,
xcb_generic_error_t **e);
β Reply accessors
int xcb_sync_list_system_counters_counters_length(const
xcb_sync_list_system_counters_reply_t *reply);
xcb_sync_systemcounter_iterator_t
xcb_sync_list_system_counters_counters_iterator(const
xcb_sync_list_system_counters_reply_t *reply);
π REQUEST ARGUMENTS π
connβ the XCB connection to X11. your lil phone line to the server, basically. main character energy fr fr.
π REPLY FIELDS π
response_typeβ the type of this reply, in this caseXCB_SYNC_LIST_SYSTEM_COUNTERS. this field is also present in thexcb_generic_reply_tand can be used 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.lengthβ the length of the reply, in words (a word is 4 bytes). yes bestie, 4 bytes. not vibes, bytes.counters_lenβ TODO: NOT YET DOCUMENTED. the manpage said what it said, we don't make stuff up here π
π· DESCRIPTION π·
lowkey the original DESCRIPTION section is empty. nothing. a blank canvas. the silence is loud π so we move on with grace and dignity.
π«Ά RETURN VALUE π«Ά
Returns an xcb_sync_list_system_counters_cookie_t. Errors have to be handled when calling the reply function xcb_sync_list_system_counters_reply.
If you want to handle errors in the event loop instead, use xcb_sync_list_system_counters_unchecked. See xcb-requests(3) for details.
so like β cookie first, then you go get the actual reply. that's the whole two-step. obsessed with the drama of it β¨
π ERRORS π
This request does never generate any errors.
not one. not ever. it's the chillest request in the building π
π₯ SEE ALSO π₯
the original SEE ALSO section is empty too. no cross-refs, no crumbs. just vibes and the void π³οΈ
πΌ AUTHOR πΌ
Generated from sync.xml. Contact xcb@lists.freedesktop.org for corrections and improvements.
and that's the whole page bestie! this one came from X Version 11, shipping with libxcb 1.17.0 β so go forth, list those system counters, and remember: handle your errors, read your cookies, and never skip the reply function πβ¨ππ¦
periodt π
π¦ 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