xcb_sync_await(3)

πŸ“¦
version 1.17.0 Β· 4 versions
, in alpine 3.22, alpine 3.23, alpine 3.24, arch rolling, centos-stream 10, debian trixie, fedora 43, fedora 44, nixpkgs unstable, opensuse-leap 16.0, ubuntu questing, ubuntu resolute, ubuntu stonking

✨ xcb_sync_await β€” the XCB Requests girlies are gonna eat this one up ✨

okay bestie, welcome to xcb_sync_await(3) from the XCB Requests corner of the universe πŸ’– this page is short, it's sweet, and honestly half of it is literally just vibes and TODO notes, so let's get into it 🫢


🌸 NAME 🌸

xcb_sync_await β€” and that's it. That's the whole name section. The description line is empty, no cap, there's literally nothing after the dash 😭 iconic behaviour honestly πŸ’…


πŸ¦‹ SYNOPSIS πŸ¦‹

First things first, you gotta pull in the header:

#include <xcb/sync.h>

πŸ’« Request function πŸ’«

xcb_void_cookie_t xcb_sync_await(xcb_connection_t *conn,
       uint32_t wait_list_len, const
       xcb_sync_waitcondition_t *wait_list);

there she is πŸ‘‘ that's the whole function signature, character for character, don't @ me.


πŸŽ€ REQUEST ARGUMENTS πŸŽ€

  • conn β€” your XCB connection to X11. the link to the server, the whole reason you're here, the main character of every XCB function fr fr πŸ”₯
  • wait_list_len β€” TODO: NOT YET DOCUMENTED. yeah bestie, the docs simply did not show up to class today πŸ™ˆ the manpage says exactly that and we are NOT about to invent lore that isn't there.
  • wait_list β€” also TODO: NOT YET DOCUMENTED. πŸ’€ same energy, same honesty, no guessing.

πŸ’œ DESCRIPTION πŸ’œ

so… the DESCRIPTION section is empty. genuinely empty. nothing. a void. a blank space where the explanation should be 🫠 we are not filling that in with made-up facts because that would be lying to you and you deserve better, bestie ✨


⭐ RETURN VALUE ⭐

she returns an xcb_void_cookie_t πŸ’… and any errors (if there are any, like, hypothetically) have to be handled over in the event loop. that's the deal, that's the contract.

if you're the kind of girlie who wants to handle errors directly with xcb_request_check instead of waiting around in the event loop, then you want xcb_sync_await_checked β€” that's the checked version of this exact request 🫢

peep xcb-requests(3) for the full details on how request handling works, iykyk πŸ“–


🌈 ERRORS 🌈

This request does never generate any errors.

never. zero. none. no error girlies here, she's clean, she's well-behaved, she does not start drama 😌🌸


🧚 SEE ALSO 🧚

nothing listed. empty section. that's just what the page says, bestie β€” I'm not gonna sneak in references that weren't there πŸ’–


πŸ‘‘ AUTHOR πŸ‘‘

Generated from sync.xml. πŸ“

If you've got corrections or improvements, hit up xcb@lists.freedesktop.org β€” they want to hear from you, fr fr 🫢


and that's the whole page, bestie!! πŸ’– this one came to you courtesy of X Version 11 and libxcb 1.17.0 β€” shoutout to the libxcb girlies, they ate and left no crumbs βœ¨πŸŽ€ mwah, see you in the next manpage πŸ’…πŸ¦‹