xcb_dpms_capable(3)

💅 xcb_dpms_capable — from the XCB Requests manual, bestie

okay so. welcome to xcb_dpms_capable(3), which is one of those lil XCB request pages, and yes the NAME line is literally just the function name with nothing after the dash. iconic of it, honestly. empty description, no notes, just vibes 🫶

---

✨ NAME ✨

xcb_dpms_capable — and that's it. that's the whole name section. the original leaves the description blank after the dash, so we're leaving it blank too. not me respecting the emptiness 💀

---

🌸 SYNOPSIS 🌸

#include <xcb/dpms.h>

🎀 Request function

xcb_dpms_capable_cookie_t xcb_dpms_capable(xcb_connection_t *conn,

yes bestie, the original really does trail off right there with a comma. we are NOT fixing it. character-for-character, periodt.

🦋 Reply datastructure

typedef struct xcb_dpms_capable_reply_t {
    uint8_t  response_type;
    uint8_t  pad0;
    uint16_t sequence;
    uint32_t length;
    uint8_t  capable;
    uint8_t  pad1[23];
} xcb_dpms_capable_reply_t;

look at her. she's got padding, she's got a capable byte, she's structured. main character energy fr fr 👑

⭐ Reply function

xcb_dpms_capable_reply_t *xcb_dpms_capable_reply(xcb_connection_t *conn,
       xcb_dpms_capable_cookie_t cookie, xcb_generic_error_t **e);

---

🌈 REQUEST ARGUMENTS 🌈

• conn — the XCB connection to X11. that's your lil phone line to the server, bestie ☎️

---

💖 REPLY FIELDS 💖

• response_type — the type of this reply, and in this case it's XCB_DPMS_CAPABLE. this field also shows up in the xcb_generic_reply_t, and it's how you tell replies apart from each other. it's the name tag at the party 🏷️
• sequence — the sequence number of the last request the X11 server processed. the receipts, basically 🧾
• length — how long the reply is, in words (and a word is 4 bytes, no cap). so do the math, don't guess 📏
• capable — TODO: NOT YET DOCUMENTED. yeah. the manpage itself says that. not me adding lore that isn't there 🙈

---

✨ DESCRIPTION ✨

genuinely nothing here. the section exists, the content does not. she's a mystery, she's an enigma, she's a blank page 💀

---

🫶 RETURN VALUE 🫶

Returns an xcb_dpms_capable_cookie_t. that's your lil claim ticket, and you gotta handle errors when you call the reply function xcb_dpms_capable_reply.

but if you'd rather handle errors in the event loop instead? use xcb_dpms_capable_unchecked. see xcb-requests(3) for the details, iykyk 💅

---

🔥 ERRORS 🔥

This request does never generate any errors.

so chill. she's safe. no drama, no errors, we love a low-maintenance request 🧚

---

🌸 SEE ALSO 🌸

also empty in the original, bestie. nothing linked, nothing referenced. we simply do not gatekeep because there is nothing to gatekeep 😭

---

👑 AUTHOR 👑

Generated from dpms.xml. Contact xcb@lists.freedesktop.org for corrections and improvements.

---

and that's the whole page, bestie! slay ✨ this was X Version 11, libxcb 1.17.0 — and the date slot is just sitting there empty like the DESCRIPTION section, so we're matching that energy fr fr. go forth and DPMS-check responsibly 💜🦋