xcb_sync_change_alarm(3)
β¨ xcb_sync_change_alarm β¨
okay bestie, so this one is from the XCB Requests part of the family β it's xcb_sync_change_alarm, a manual page from libxcb. Yes the NAME section in the original is literally just the function name and then nothing, because sometimes the manpage authors leave us on read. π We still love her.
πΈ SYNOPSIS πΈ
first, you gotta pull in the header:
#include <xcb/sync.h>
π Request function
xcb_void_cookie_t xcb_sync_change_alarm(xcb_connection_t *conn,
xcb_sync_alarm_t id, uint32_t value_mask, const
void *value_list);
she returns a xcb_void_cookie_t, so like β she's not handing you data back directly, she's handing you a receipt. π§Ύ
π¦ REQUEST ARGUMENTS π¦
connβ the XCB connection to X11. your whole lil portal to the X server, iconic.idβTODO: NOT YET DOCUMENTED.π yeah. the docs said "we'll get to it" and then did not get to it.value_maskβTODO: NOT YET DOCUMENTED.also left blank. the audacity.value_listβTODO: NOT YET DOCUMENTED.same energy, bestie. all three of these are still waiting for their moment.
no cap: the original manpage genuinely leavesid,value_maskandvalue_listundocumented. i'm not gatekeeping anything from you β there is nothing there to gatekeep. π
π DESCRIPTION π
the DESCRIPTION section is empty in the original. nothing. void. xcb_void_cookie_t vibes, honestly β it's giving she said nothing and left. π«Ά
π RETURN VALUE π
she gives you back an xcb_void_cookie_t. any errors (if there even are any) have to be handled over in the event loop, not right here.
if you'd rather deal with errors directly using xcb_request_check instead, then use xcb_sync_change_alarm_checked β that's the checked twin. π see xcb-requests(3) for the full tea on how requests work.
π₯ ERRORS π₯
this request does never generate any errors. not one. zero. a clean queen. π
β SEE ALSO β
the SEE ALSO section is empty in the original β no cross-references listed. she stands alone. main character energy fr fr.
π AUTHOR π
generated from sync.xml. for corrections and improvements, contact xcb@lists.freedesktop.org β they're the ones you @ when something's off. π
and that's the whole page, bestie!! this one came to you from X Version 11, libxcb 1.17.0, under the name xcb_sync_change_alarm(3) β go forth and change those alarms, or at least change the ones whose arguments got documented. 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