xcb_xevie_start(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_xevie_start 💖

okay so bestie, this is the xcb_xevie_start page from the XCB Requests crew — it lives in section 3 of the manual, and it's literally just vibes and a cookie. Let's get into it 🫶

✨ NAME ✨

xcb_xevie_start -

yeah bestie the description is genuinely empty, that's not me being lazy, that's the whole name section, periodt 💀

✨ SYNOPSIS ✨

#include <xcb/xevie.h>

🌸 Request function 🌸

xcb_xevie_start_cookie_t xcb_xevie_start(xcb_connection_t *conn,
       uint32_t screen);

🎀 Reply datastructure 🎀

typedef struct xcb_xevie_start_reply_t {
    uint8_t  response_type;
    uint8_t  pad0;
    uint16_t sequence;
    uint32_t length;
    uint8_t  pad1[24];
} xcb_xevie_start_reply_t;

🦋 Reply function 🦋

xcb_xevie_start_reply_t *xcb_xevie_start_reply(xcb_connection_t *conn,
       xcb_xevie_start_cookie_t cookie, xcb_generic_error_t **e);

✨ REQUEST ARGUMENTS ✨

  • conn — the XCB connection to X11, your little phone line to the server, no cap 💅
  • screen — TODO: NOT YET DOCUMENTED. yeah girl, they just never wrote it. it's giving mystery. we move on 🙈

✨ REPLY FIELDS ✨

  • response_type — the type of this reply, which in this case is XCB_XEVIE_START. this field is also chillin' inside xcb_generic_reply_t, so you can use it to tell your replies apart from each other 👑
  • sequence — the sequence number of the last request that the X11 server processed. it's the receipts, basically 🧾
  • length — the length of the reply, in words (and a word here is 4 bytes, so do the math bestie) 📏

✨ DESCRIPTION ✨

…nothing. literally nothing. the DESCRIPTION section is empty, and honestly? iconic of it. 😭

✨ RETURN VALUE ✨

It hands you back an xcb_xevie_start_cookie_t. 🍪

Errors have to be handled when you call the reply function xcb_xevie_start_reply.

If you'd rather handle errors in the event loop instead, use xcb_xevie_start_unchecked. See xcb-requests(3) for the details, bestie, that's where the lore lives 📚

✨ ERRORS ✨

good news!! this request does never generate any errors. zero drama, zero chaos, we love a low-maintenance request ✨

✨ SEE ALSO ✨

(empty. nothing here. just vibes and open space 🌈)

✨ AUTHOR ✨

Generated from xevie.xml. Contact xcb@lists.freedesktop.org for corrections and improvements — so if you spot something wrong, fr fr email them, they're nice about it 💌

okay that's the whole page bestie, ily, go forth and call your request 💖✨

this came to you from X Version 11, libxcb 1.17.0, and the xcb_xevie_start(3) page itself — slay, bye!! 🎀🦋💅

📦 where this page comes from