XCB_PRESENT_QUERY_CAPABILITIES_UNCHECKED(3)

💅 xcb_present_query_capabilities — a whole manual page, bestie

okay so this is xcb_present_query_capabilities(3) from the XCB Requests family, and honestly? she's a lil mysterious. let's get into it 🫶

---

✨ NAME ✨

xcb_present_query_capabilities

and that's... it. that's the whole name section. no little one-line summary, nothing. the manpage authors left it blank like a text they forgot to send 😭 we move.

---

🌸 SYNOPSIS 🌸

first things first, you gotta pull in the header:

#include <xcb/present.h>

🎀 Request function

xcb_present_query_capabilities_cookie_t
       xcb_present_query_capabilities(xcb_connection_t *conn,
       uint32_t target);

🦋 Reply datastructure

typedef struct xcb_present_query_capabilities_reply_t {
    uint8_t  response_type;
    uint8_t  pad0;
    uint16_t sequence;
    uint32_t length;
    uint32_t capabilities;
} xcb_present_query_capabilities_reply_t;

⭐ Reply function

xcb_present_query_capabilities_reply_t
       *xcb_present_query_capabilities_reply(xcb_connection_t *conn,
       xcb_present_query_capabilities_cookie_t cookie,
       xcb_generic_error_t **e);

---

💖 REQUEST ARGUMENTS 💖

• conn — the XCB connection to X11. your lil phone line to the server, basically. 📞
• target — TODO: NOT YET DOCUMENTED. yeah. nobody wrote it down. it's giving mystery novel 🔍

---

🌈 REPLY FIELDS 🌈

• response_type — the type of this reply, and in this case it's XCB_PRESENT_QUERY_CAPABILITIES. this field also lives in the xcb_generic_reply_t, so you can use it to tell your replies apart from each other — like name tags at a party, but for packets 👑
• sequence — the sequence number of the last request processed by the X11 server. the receipts, basically 🧾
• length — the length of the reply, in words (and a word is 4 bytes, no cap) 📏
• capabilities — TODO: NOT YET DOCUMENTED. the suspense is unreal 💀

---

🌸 DESCRIPTION 🌸

this section is empty in the original. nothing here. a void. an aesthetic little void ✨

---

🫶 RETURN VALUE 🫶

you get back an xcb_present_query_capabilities_cookie_t. cute, right? but here's the thing — errors have to be handled when you call the reply function, xcb_present_query_capabilities_reply. that's where the actual tea gets spilled 🍓

and if you'd rather handle errors inside the event loop instead? use xcb_present_query_capabilities_unchecked. details live in xcb-requests(3), go read her 💜

---

💀 ERRORS 💀

good news bestie: this request does never generate any errors. zero. none. immaculate behaviour. periodt. 👑

---

🔥 SEE ALSO 🔥

also empty in the original. no cross-references, no friends, just vibes 🙈

---

🧚 AUTHOR 🧚

Generated from present.xml. Contact xcb@lists.freedesktop.org for corrections and improvements. (yes, they're asking you to email them. they're so real for that 📧)

---

X Version 11 · libxcb 1.17.0 · and that's the whole page, mwah 💋 stay hydrated, read your manpages, and remember: a word is 4 bytes, no cap 💅✨