xcb_sync_destroy_alarm(3)

💅 xcb_sync_destroy_alarm — bestie's guide to yeeting an alarm 💅

okay so this is a page from the XCB Requests part of the libxcb manual (you'll see xcb_sync_destroy_alarm(3) up in the corner, that's the whole title, she's lowkey self-explanatory). sit down, grab a strawberry 🍓, we're learning how to delete a sync alarm in X11.

---

✨ NAME ✨

xcb_sync_destroy_alarm —

not gonna lie to you bestie, the description slot here is literally empty. the original manpage just trails off. no cap. so the name is just the name, and we move. 🙈

---

✨ SYNOPSIS ✨

#include <xcb/sync.h>

🎀 Request function

xcb_void_cookie_t xcb_sync_destroy_alarm(xcb_connection_t *conn,
       xcb_sync_alarm_t alarm);

it's giving "one function, two arguments, zero drama" 💖

---

✨ REQUEST ARGUMENTS ✨

• conn — the XCB connection to X11. that's your lil phone line to the X server, the main character of every single XCB function fr fr 🔥
• alarm — TODO: NOT YET DOCUMENTED. 😭 that's not me being lazy, that's literally what the original says. the docs just never got written for this one. iconic of them honestly.

---

✨ DESCRIPTION ✨

okay so… the DESCRIPTION section of the original is completely empty. nothing. not one word. a blank canvas. a vibe. 💀

i'm not gonna invent behaviour for you because that would be lying and we don't do that here. all we know is what's above and below. periodt.

---

✨ RETURN VALUE ✨

she hands you back an xcb_void_cookie_t. ✨ that's your lil receipt. and bestie, listen — any errors (if there even are any) have to be handled in the event loop. you don't get them handed to you directly, you gotta go pick them up yourself.

if you'd rather handle errors directly with xcb_request_check instead, then use xcb_sync_destroy_alarm_checked — that's the version with the safety rails. see xcb-requests(3) for the details, she explains the whole cookie situation way better than i can. 🫶

---

✨ ERRORS ✨

this request does never generate any errors. 🎉 zero. none. not a single one. she's a good girl, she causes no problems, she simply vibes. 🌈

---

✨ SEE ALSO ✨

bestie… the original has nothing here either. an empty SEE ALSO section. the audacity. 😭 so i got nothing to point you at — the real content lives in xcb-requests(3) (mentioned above in RETURN VALUE) and that's genuinely it.

---

✨ AUTHOR ✨

generated from sync.xml. 📄 if you spot something wrong or wanna make it better, contact xcb@lists.freedesktop.org — they take corrections and improvements, so don't be shy, send that email, you got this. 💜

---

and that's the whole page, bestie!! 🌸 short one today, mostly because the original manpage left half its sections empty and we're nothing if not faithful to the source. slay. 💅

this has been brought to you by X Version 11, libxcb 1.17.0, and the xcb_sync_destroy_alarm(3) era of your life. stay hydrated, read your manpages, and may your cookies never error out. byeee 🦋✨