xcb_xevie_end(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_end — bestie we are ENDING things 💅

okay so real talk, this is a page from XCB Requests, and the function itself is xcb_xevie_end. That's it. That's the whole NAME section. She's mysterious, she's lowkey giving nothing, and honestly? Iconic behaviour. 🎀

🌸 SYNOPSIS 🌸

first things first, you gotta pull in the header, no cap:

#include <xcb/xevie.h>

💖 Request function

xcb_xevie_end_cookie_t xcb_xevie_end(xcb_connection_t *conn,
       uint32_t cmap);

🦋 Reply datastructure

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

🌈 Reply function

xcb_xevie_end_reply_t *xcb_xevie_end_reply(xcb_connection_t *conn,
       xcb_xevie_end_cookie_t cookie, xcb_generic_error_t **e);

🫶 REQUEST ARGUMENTS

  • conn — your XCB connection to X11, the group chat you're sending all this into 💌
  • cmap — TODO: NOT YET DOCUMENTED. yeah bestie, the docs said "we'll get to it" and then never did 😭 not me being honest about it

👑 REPLY FIELDS

  • response_type — the type of this reply, which in this case is XCB_XEVIE_END. This field also lives in xcb_generic_reply_t, and it's literally the way you tell your replies apart from each other, so don't skip it ✨
  • sequence — the sequence number of the last request the X11 server actually got around to processing 🔢
  • length — how long the reply is, in words (and reminder: a word is 4 bytes, always) 📏

💜 DESCRIPTION

…and that's the whole section. Empty. Nothing. A vibe. The DESCRIPTION said nothing and left the party early 🫥 (keeping it 100% real with you, there is genuinely no description text on this page.)

🔥 RETURN VALUE

You get back an xcb_xevie_end_cookie_t. That's a cookie, bestie — the request is out the door but the answer hasn't come back yet. Errors have to be handled when you call the reply function xcb_xevie_end_reply, so don't just fire and forget and act surprised later 💀

If you'd rather deal with your errors in the event loop instead, then use xcb_xevie_end_unchecked. Peep xcb-requests(3) for the full tea on how that works ☕

💀 ERRORS

This request does never generate any errors. Not one. Zero. She is unproblematic and we love that for her 🕊️

🎀 SEE ALSO

(Yeah, that's the only one. She keeps her circle small 💅)

🙈 AUTHOR

Generated from xevie.xml. If you spot something wrong and wanna fix it or improve it, hit up xcb@lists.freedesktop.org — they're the ones who take corrections and improvements, and they'd be so grateful fr fr 💌

and that's a wrap, bestie!! this lil' cutie came to you from X Version 11 and libxcb 1.17.0 — mwah, slay, go end some things responsibly 🦋✨

📦 where this page comes from