xcb_sync_destroy_fence(3)
π xcb_sync_destroy_fence β from the XCB Requests collection, section 3, bestie π
okay so hi!! you're looking at the manual page for xcb_sync_destroy_fence, and it lives in manual section 3 with all the other XCB Requests pages. she's a libxcb girlie, she's part of X Version 11, and honestly? she's a whole vibe. let's get into it π¦
β¨ NAME β¨
xcb_sync_destroy_fence -
fr fr that's it. that trailing dash is just... hanging there. the description slot is empty. not me staring at a blank line π
πΈ SYNOPSIS πΈ
#include <xcb/sync.h>
π«Ά Request function
xcb_void_cookie_t xcb_sync_destroy_fence(xcb_connection_t *conn,
xcb_sync_fence_t fence);
that's the whole signature, no cap. two args, one cookie, zero drama (well, almost zero β keep reading) β¨
π REQUEST ARGUMENTS π
connβ the XCB connection to X11. it's your little hotline to the X server, your main character link-up π₯fenceβTODO: NOT YET DOCUMENTED.yeah bestie, the docs literally say that. iconic of them honestly. we do not know what this fence is. we simply pass it π
π¦ DESCRIPTION π¦
so... there is no description here. the section exists, it's just empty. the manual page woke up, put on its outfit, and said nothing. lowkey mysterious, highkey iconic π
(that's genuinely all the original gives us β no extra lore, no secret tea, don't let anyone tell you otherwise π)
π RETURN VALUE π
it hands you back an xcb_void_cookie_t. that's it, that's the whole return situation.
errors (if any β and honestly, see below) have to be handled in the event loop. like, you don't get them handed to you right here, you go catch them later.
but!! if you'd rather handle errors directly with xcb_request_check instead, then use xcb_sync_destroy_fence_checked β she's the checked version, she's built different π
for the full tea on how requests and their errors work, see xcb-requests(3). required reading, no skips π
π ERRORS π
this request does never generate any errors. periodt. not one. zero. the cleanest girl at the function πΈ
π§ SEE ALSO π§
nothing here either bestie π the section is present and correct and completely empty. we love a minimalist queen.
π AUTHOR π
Generated from sync.xml. Contact xcb@lists.freedesktop.org for corrections and improvements. π«Ά
and that's the page!! go forth and destroy that fence, whatever she is πβ¨
this was libxcb 1.17.0, X Version 11, and yes the section-3 girly xcb_sync_destroy_fence(3) β mwah, 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