xcb_sync_trigger_fence(3)
β¨ NAME β¨
xcb_sync_trigger_fence β bestie this one's a mystery even to me (the manpage literally gives no description, no cap π)
π¦ SYNOPSIS π¦
#include <xcb/sync.h>
π Request function π
xcb_void_cookie_t xcb_sync_trigger_fence(xcb_connection_t *conn,
xcb_sync_fence_t fence);
πΈ REQUEST ARGUMENTS πΈ
connβ the XCB connection to X11, aka your lil hotline to the X server, she's the main character here πfenceβ TODO: NOT YET DOCUMENTED. yeah babe I know, the docs said nothing, we're all just out here living the same unhinged life π
π DESCRIPTION π
okay soβ¦ there is literally no description in the source. Zero. Zilch. The DESCRIPTION section is out here giving absolutely nothing, an empty plate, a vibe check with no vibes. π
Not me having to tell you that the official docs left this blank, but here we are β I'm nothing if not honest with my bestie. π«Ά
π₯ RETURN VALUE π₯
She returns an xcb_void_cookie_t. Iconic. Effortless. No notes. β¨
If any errors show up (like, if β see below, girl), you have to handle them in the event loop, that's just the rules of the house π
But if you'd rather handle errors directly with xcb_request_check instead, then bestie you want the xcb_sync_trigger_fence_checked version, she's right there waiting for you π
For all the deets on how this whole cookie thing works, go read xcb-requests(3) β she explains it way better than I can in one breath β
π ERRORS π
This request does never generate any errors. Periodt. Not a single one. She's unproblematic, she's chill, she's never giving you drama π₯
π SEE ALSO π
(nothing here either bestie β the source page is empty in this section, so I'm not about to invent references for you. Iykyk. π)
π AUTHOR π
Generated from sync.xml. If you spot something wrong or want to send improvements, contact xcb@lists.freedesktop.org β they're the ones who actually know stuff, unlike this DESCRIPTION section π
okay so that's the whole page, we did it, we survived the mystery fence request together π X Version 11, libxcb 1.17.0 β that's the version and source for this very page, and yes I'm mentioning it in a cute sign-off instead of a boring footer, because we are not boring. Mwah. πβ¨
π¦ 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