xcb_sync_destroy_counter(3)
π xcb_sync_destroy_counter β the XCB Requests girlies' guide π
okay so bestie, welcome to xcb_sync_destroy_counter(3), part of the XCB Requests family. yes the NAME section is literally just the function name and a lil dash with nothing after it β she's mysterious like that, we respect it π
β¨ SYNOPSIS β¨
first thing's first, you gotta invite her in:
#include <xcb/sync.h>
Request function
xcb_void_cookie_t xcb_sync_destroy_counter(xcb_connection_t *conn,
xcb_sync_counter_t counter);
that's it, that's the whole summoning ritual π
πΈ REQUEST ARGUMENTS πΈ
connβ the XCB connection to X11. she's the link between you and the server, the group chat if you will π«Άcounterβ TODO: NOT YET DOCUMENTED. yeah ngl the docs just left her on read π the XCB authors never filled this one in. we're not gonna pretend otherwise. she's anxcb_sync_counter_t, that's all we know fr fr.
π¦ DESCRIPTION π¦
soβ¦ the DESCRIPTION section is literally empty. not one word. it's giving vibes only, no info. iconic of her honestly π the function name does all the talking: you're destroying a sync counter. the rest is between you and the universe β¨
π RETURN VALUE π
she hands you back an xcb_void_cookie_t. that's right β a void cookie, so there's no actual value waiting inside, but errors (if any) have to be handled in the event loop, bestie. don't go looking for them anywhere else, they don't come home in the cookie.
and okay, if you're the type who wants to handle errors directly with xcb_request_check instead of doing the whole event loop dance β valid! β then use xcb_sync_destroy_counter_checked instead. that's the checked twin, she's right there. see xcb-requests(3) for the full tea on how that works π
π ERRORS π
this request never generates any errors. zero. none. not a single one. she's drama-free, she's unbothered, she could never π no cap.
but like β still check your cookies properly, that's just good manners π
π SEE ALSO π
(nothing listed here, bestie β the SEE ALSO section is empty. we looked. she's a lone wolf πΊ)
π AUTHOR π
Generated from sync.xml. if something's wrong or you wanna make it better, contact xcb@lists.freedesktop.org for corrections and improvements β they actually want your feedback, no cap π«Ά
okay that's the whole page, you're officially certified in destroying sync counters now, go be the main character of your own X session β
this lil masterpiece came from X Version 11 / libxcb 1.17.0, and yeah the header up top said xcb_sync_destroy_counter(3) β love that for her π bye bestie!! π¦β¨
π¦ 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