xcb_sync_get_priority(3)

💅 xcb_sync_get_priority — the manual page, but make it cute

okay bestie, welcome to xcb_sync_get_priority(3) — it's from the XCB Requests corner of the universe and it's literally here to read a priority value off your X11 server. no thoughts, just vibes and a cookie. let's get into it 🎀

---

✨ NAME ✨

xcb_sync_get_priority — (the name section is literally just a dash in the original, so we're keeping it mysterious. iconic behaviour honestly)

---

🦋 SYNOPSIS 🦋

first things first, you gotta include the header:

#include <xcb/sync.h>

Request function (the main character)

xcb_sync_get_priority_cookie_t
xcb_sync_get_priority(xcb_connection_t *conn, uint32_t id);

Reply datastructure (the lil container, she's got range)

typedef struct xcb_sync_get_priority_reply_t {
    uint8_t  response_type;
    uint8_t  pad0;
    uint16_t sequence;
    uint32_t length;
    int32_t  priority;
} xcb_sync_get_priority_reply_t;

Reply function (where you actually get the tea ☕)

xcb_sync_get_priority_reply_t
*xcb_sync_get_priority_reply(xcb_connection_t *conn,
xcb_sync_get_priority_cookie_t cookie, xcb_generic_error_t **e);

---

💖 REQUEST ARGUMENTS 💖

• conn — your XCB connection to X11. she's the whole portal, the link-up, the way you even talk to the server. no conn, no convo 🫶
• id — TODO: NOT YET DOCUMENTED. yeah bestie, the original really said that. we don't know what this id is. it's giving mystery. we keep it honest, we don't make stuff up 💀

---

🌸 REPLY FIELDS 🌸

• response_type — the type of this reply. in this specific case it's XCB_SYNC_GET_PRIORITY. this field also lives inside the xcb_generic_reply_t, which is lowkey handy because it lets you tell your replies apart from each other. sorting hat energy.
• sequence — the sequence number of the last request that got processed by the X11 server. like a lil "you are here" sticky note ✨
• length — the length of the reply, measured in words. and before you ask: a word is 4 bytes. that's the rule, no cap.
• priority — TODO: NOT YET DOCUMENTED. again. the original is not beating the mysterious allegations. we are not inventing lore for it. 🙈

---

🌈 DESCRIPTION 🌈

the original DESCRIPTION section is… empty. like, nothing. a blank. a vibe void. so there's nothing to relay here, and we're not about to make up technical claims, because that would be a lie and lying about manpages is not the move. periodt. 💅

---

⭐ RETURN VALUE ⭐

you get back an xcb_sync_get_priority_cookie_t. that's the cookie 🍪 — hold onto it, because any errors have to be handled when you call the reply function xcb_sync_get_priority_reply.

now, if you'd rather handle your errors in the event loop instead of right at the reply call, use xcb_sync_get_priority_unchecked. and for all the deets on how that works, go peek at xcb-requests(3). iykyk 💜

---

🎀 ERRORS 🎀

this request does never generate any errors. not one. zero. she's unproblematic, she's chill, she's never starting drama in the error channel. slay. 👑

---

🔥 SEE ALSO 🔥

(the SEE ALSO section in the original is empty too — so there are no references listed here. nothing to link, nothing to chase. she's self-sufficient.)

---

👑 AUTHOR 👑

generated from sync.xml. if you spot something wrong or wanna suggest corrections and improvements, hit up xcb@lists.freedesktop.org. the original says it, so we say it. that's the chain of command 🫡

---

okay that's the whole page, bestie, you ate that. 💖✨

and for the cute sign-off: this page is part of X Version 11, sitting at libxcb 1.17.0, and it's filed under xcb_sync_get_priority(3) — go forth and read your priorities responsibly 🦋🌸