xcb_xevie_send(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_send — XCB Requests 💖

okay so bestie, welcome to the xcb_xevie_send manual page, from the XCB Requests crew. buckle up, it's giving ✨ X11 ✨ and we're gonna read it together, no cap.

🌸 NAME 🌸

xcb_xevie_send —

(yes the description is literally empty up there, the original said nothing, so I'm saying nothing too. iconic behaviour honestly 💅)

🦋 SYNOPSIS 🦋

#include <xcb/xevie.h>

💫 Request function

xcb_xevie_send_cookie_t xcb_xevie_send(xcb_connection_t *conn,
       xcb_xevie_event_t event, uint32_t data_type);

🎀 Reply datastructure

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

🌈 Reply function

xcb_xevie_send_reply_t *xcb_xevie_send_reply(xcb_connection_t *conn,
       xcb_xevie_send_cookie_t cookie, xcb_generic_error_t **e);

👑 REQUEST ARGUMENTS 👑

  • conn — the XCB connection to X11, aka your lil hotline to the server, she's the main character fr fr.
  • event — TODO: NOT YET DOCUMENTED. 😭 bestie the docs said "we'll get to it", and then they did not get to it. we love that for them.
  • data_type — TODO: NOT YET DOCUMENTED. same energy, same empty vibes, I'm just the messenger 🫶

🧚 REPLY FIELDS 🧚

  • response_type — the type of this reply, and in this case it's XCB_XEVIE_SEND. this field is also chillin' in the xcb_generic_reply_t, so you can use it to tell your replies apart from each other. lowkey a bouncer checking IDs at the reply club 💅
  • sequence — the sequence number of the last request the X11 server got around to processing. it's the server's "read receipt", periodt.
  • length — the length of the reply, in words. and a word here is 4 bytes, so do not come at me with your English-major definition of "word", this is the C kind. 💀

💜 DESCRIPTION 💜

so this section is... empty. like genuinely empty. the original page had nothing under DESCRIPTION and I refuse to make up lore that isn't there, that's not the vibe. no notes, just vibes. 🙈

⭐ RETURN VALUE ⭐

Returns an xcb_xevie_send_cookie_t. 🍪 (a cookie, bestie, not the edible kind, it's how XCB does async.)

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

But if you'd rather handle your errors in the event loop instead, then use xcb_xevie_send_unchecked. See xcb-requests(3) for the details, she explains it better than me.

💀 ERRORS 💀

This request does never generate any errors.

read that again. NEVER. not one. she's an angel, she simply does not miss. slay. 🔥

🌟 SEE ALSO 🌟

(also empty in the original, so it's empty here too. nothing to link, nothing to click, just us and the void ✨)

🩷 AUTHOR 🩷

Generated from xevie.xml. Contact xcb@lists.freedesktop.org for corrections and improvements. be nice to them, they're doing their best 🫶

and that's the whole page bestie!! sending you the biggest 💖 for making it to the end. this little icon came from X Version 11, libxcb 1.17.0, filed under xcb_xevie_send(3) — and if you ever need her again, she's right there in your man pages. go forth and slay your X11 session, ily 💅✨

📦 where this page comes from