xcb_sync_set_counter(3)
π xcb_sync_set_counter π
okay so bestie, welcome to the manual page for xcb_sync_set_counter(3) β that's the one, that's the girl, she's part of the XCB Requests gang and she's here to set a counter. no cap. β¨
β¨ NAME β¨
xcb_sync_set_counter β the name says it all and also says nothing, we love a mysterious queen π
πΈ SYNOPSIS πΈ
first up, you gotta pull in the header or nothing works, obviously:
#include <xcb/sync.h>
π Request function π
xcb_void_cookie_t xcb_sync_set_counter(xcb_connection_t *conn,
xcb_sync_counter_t counter, xcb_sync_int64_t value);
look at her. three args, one cookie, zero drama. iconic.
π¦ REQUEST ARGUMENTS π¦
connβ the XCB connection to X11. your little pipeline to the X server, your main character linkup, you already know π«Άcounterβ TODO: NOT YET DOCUMENTED. yeah. the docs said "we'll get to it" and then did not get to it π not me reading a TODO in a manpage in the year of our lordvalueβ TODO: NOT YET DOCUMENTED. same energy, same blank stare, the mystery continues π₯
π DESCRIPTION π
so here's the thing bestie... this section is literally empty. no prose. no lore. no vibe. just the heading sitting there looking pretty π the DESCRIPTION of this request is a void and we respect the void's privacy.
β RETURN VALUE β
she hands you back an xcb_void_cookie_t. that's it, that's the whole return, no payload, just a little receipt π§Ύ
and listen, because this matters: errors (if any) have to be handled in the event loop. you do not get to just ignore them and walk away, okay? handle them. in the event loop. where they live.
if you'd rather catch errors directly with xcb_request_check instead, then you want the checked version: xcb_sync_set_counter_checked. same girl, slightly different personality. peek xcb-requests(3) for the details π
π ERRORS π
good news for once: this request does never generate any errors. zero. none. nothing. she's unproblematic, she's low maintenance, she's the friend who never starts drama πΈ
π SEE ALSO π
...and that's it, that's the list. empty. nothing to see here, no cross-references, no friends of hers, just a lonely heading vibing in the corner π
π AUTHOR π
Generated from sync.xml. if you spot something wrong and wanna send corrections and improvements, hit up xcb@lists.freedesktop.org β they're taking notes, bestie, and they want yours π
okay and finally, the cute sign-off because we always do the cute sign-off: this whole thing comes to you from X Version 11, running on libxcb 1.17.0, under the name xcb_sync_set_counter(3) π go set a counter, you absolute legend, ily, bye πβ¨
π¦ 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