xcb_sync_await_fence(3)

✨ NAME ✨

xcb_sync_await_fence — okay bestie, this is an XCB request from the sync corner of the X11 universe, and the official docs literally left the description blank, so we're gonna keep it 💯 honest about that. It's the "await fence" request, it lives in libxcb, and it's part of the whole XCB requests family. That's the whole vibe. 🎀

---

🌸 SYNOPSIS 🌸

First things first, you gotta pull in the header, no cap:

#include <xcb/sync.h>

💅 Request function

Here's the actual signature, character for character, don't @ me:

xcb_void_cookie_t xcb_sync_await_fence(xcb_connection_t *conn,
       uint32_t fence_list_len, const xcb_sync_fence_t *fence_list);

---

🦋 REQUEST ARGUMENTS 🦋

• conn — the XCB connection to X11, aka your lil pipeline to the server. Everything goes through this bb. 🔥
• fence_list_len — TODO: NOT YET DOCUMENTED. Yeah. The upstream docs said "not yet documented" and honestly? They ate with the honesty. 🙈
• fence_list — TODO: NOT YET DOCUMENTED. Same energy. We are not making stuff up here, periodt. 💀

---

🌈 DESCRIPTION 🌈

So here's the tea, and it's a short cup: this section is empty in the original page. There's literally no prose describing what this request does. Not a single word. It's giving mystery main character energy. 👑

Real talk: I'm not gonna invent a description for you, because the rule is every detail kept, nothing added. If upstream hasn't written it, I'm not cosplaying as someone who knows. That's the whole integrity vibe. 💖

---

⭐ RETURN VALUE ⭐

It hands you back an xcb_void_cookie_t. 🫶

And here's the important bit, bestie — if there are errors (any at all), you do not get them handed to you right here. You gotta handle them in the event loop. That's just how the void-cookie life works.

But wait — if you'd rather deal with errors directly with xcb_request_check instead, then you want the checked version: xcb_sync_await_fence_checked. Easy swap, same request, different energy. ✨

And if you want the full lore on how cookies and requests work, go read xcb-requests(3). It's the required reading, iykyk. 📚

---

😭 ERRORS 😭

This request does never generate any errors.

That's it. That's the whole section. Zero errors, zero drama, absolutely unbothered. 💅

---

🔥 SEE ALSO 🔥

Nothing listed here in the original — the section is empty, so we're keeping it empty. No invented cross-references, no extra links, nothing. Clean. 🌸

---

💜 AUTHOR 💜

Generated from sync.xml. If you spot something wrong or wanna send improvements, hit up xcb@lists.freedesktop.org — they're the ones who take corrections and improvements. Be nice, be specific, slay. 🎀

---

And that's the page, babe! This manual came from <b>X Version 11</b>, <b>libxcb 1.17.0</b>, for xcb_sync_await_fence(3). Go forth and await those fences, bestie — ily, stay documented! 🦋✨