xcb_sync_initialize(3)
π xcb_sync_initialize π
okay bestie, welcome to the xcb_sync_initialize page β it lives in the XCB Requests corner of the manual (section 3, for all you keeping score at home) π . It's giving β¨sync extension handshakeβ¨ and honestly? We're obsessed.
β¨ NAME β¨
xcb_sync_initialize β no description here, the original literally just leaves it blank, and we respect the mystery π«Ά
πΈ SYNOPSIS πΈ
#include <xcb/sync.h>
π Request function π
xcb_sync_initialize_cookie_t xcb_sync_initialize(xcb_connection_t *conn,
uint8_t desired_major_version, uint8_t desired_minor_version);
π¦ Reply datastructure π¦
typedef struct xcb_sync_initialize_reply_t {
uint8_t response_type;
uint8_t pad0;
uint16_t sequence;
uint32_t length;
uint8_t major_version;
uint8_t minor_version;
uint8_t pad1[22];
} xcb_sync_initialize_reply_t;
β Reply function β
xcb_sync_initialize_reply_t
*xcb_sync_initialize_reply(xcb_connection_t *conn,
xcb_sync_initialize_cookie_t cookie, xcb_generic_error_t **e);
π REQUEST ARGUMENTS π
connβ the XCB connection to X11, obvi. your lil hotline to the server π₯desired_major_versionβ TODO: NOT YET DOCUMENTED. yeah bestie, the docs said "idk yet" and we're just relaying that fr fr πdesired_minor_versionβ also TODO: NOT YET DOCUMENTED. same energy, same void π
π REPLY FIELDS π
response_typeβ the type of this reply, which in this case isXCB_SYNC_INITIALIZE. This field is also chillin' inside thexcb_generic_reply_t, and you can use it to tell your replies apart from each other, like name tags at a party πsequenceβ the sequence number of the last request processed by the X11 server. it's the receipts, basically π§Ύlengthβ the length of the reply, in words. and yes, a word is 4 bytes, not a vibe πmajor_versionβ TODO: NOT YET DOCUMENTED. the plot hole remains π³οΈminor_versionβ TODO: NOT YET DOCUMENTED. same hole, different field π
π DESCRIPTION π
...there is literally nothing here. the DESCRIPTION section is empty. an absolute icon of leaving you on read. no cap, that's the whole thing π
π RETURN VALUE π
Returns an xcb_sync_initialize_cookie_t. Errors have to be handled when you call the reply function xcb_sync_initialize_reply.
If you'd rather handle errors in the event loop instead, use xcb_sync_initialize_unchecked. See xcb-requests(3) for the deets π«Ά
π ERRORS π
This request never generates any errors. not one. zero. a truly unproblematic fave, we love to see it β¨
π₯ SEE ALSO π₯
...yeah the SEE ALSO section is empty too. it's giving "no thoughts, head empty" and honestly, iconic behavior π
πΈ AUTHOR πΈ
Generated from sync.xml. Contact xcb@lists.freedesktop.org for corrections and improvements.
π«Ά quick reminder bestie: all those TODO: NOT YET DOCUMENTED. fields are straight from the source, so don't come for me, I'm just the messenger π
X Version 11 π libxcb 1.17.0 π¦ that's the version and the date-of-record, and xcb_sync_initialize(3) is the page you're on, mwah π
β¨ periodt.
π¦ 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