xcb_glx_destroy_pixmap(3)

💅 xcb_glx_destroy_pixmap — the XCB Requests girlies' moment

okay so bestie, welcome to xcb_glx_destroy_pixmap, straight out of the XCB Requests family 🎀. It's a request function, it's short, it's iconic, and honestly? It's giving "quiet luxury" because the docs for it are like 90% vibes and 10% actual text. But we're gonna walk through every single crumb anyway, because that's what besties do. 💖

---

✨ NAME ✨

xcb_glx_destroy_pixmap —

and that's it. That's the whole name line. The description slot? Empty. Blank. A little void where a summary should be. Not me staring at it like 👁️👄👁️. Anyway, the name is xcb_glx_destroy_pixmap, and that's what we're working with. Slay.

---

🌸 SYNOPSIS 🌸

First things first, you gotta pull in the header:

#include <xcb/glx.h>

🦋 Request function

xcb_void_cookie_t xcb_glx_destroy_pixmap(xcb_connection_t *conn,
       xcb_glx_pixmap_t glx_pixmap);

look at her. so clean. so simple. so lowkey. 💜

---

🍓 REQUEST ARGUMENTS 🍓

• conn — the XCB connection to X11. Your lil lifeline to the server, your group chat with the display, your whole world basically. 💫
• glx_pixmap — bestie... the manpage literally says TODO: NOT YET DOCUMENTED. 😭 Not me finding the one line in the docs that's just a sticky note someone forgot to fill in. So like, it's a xcb_glx_pixmap_t, and that's what the page gives us — no more, no less. We do NOT make things up in this house. 🙈

---

🌈 DESCRIPTION 🌈

...yeah. There isn't one. The DESCRIPTION section of this page is empty. Genuinely nothing there. It's the blank canvas, the "no thoughts, head empty" moment, the silence before the beat drops. 💀

I know, I know, you wanted lore. The lore is not here. Moving on, bestie, keep it pushing. 💅

---

⭐ RETURN VALUE ⭐

She returns an xcb_void_cookie_t. That's your little receipt 🧾 — and if any errors pop off, you have to handle them over in the event loop, not right here. That's the whole vibe of void requests.

and if you'd rather check for errors immediately instead? Use xcb_glx_destroy_pixmap_checked instead. There's a whole checked version just for that. See xcb-requests(3) for the deets, bestie. 🫶

---

💀 ERRORS 💀

Okay so plot twist:

This request does never generate any errors.

Periodt. No errors. Zero. Zilch. Not a single one. It literally cannot fail you, which is honestly the kind of loyalty we deserve in this life. 🔥👑

---

🔥 SEE ALSO 🔥

Nothing listed here. Empty. The SEE ALSO section is just... standing there. Looking at you. Saying nothing. ✨

(But hey — the RETURN VALUE section did shout out xcb-requests(3), so there's that.)

---

🧚 AUTHOR 🧚

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

like, they made it from an XML file and they want your feedback, so if you find something busted, hit them up. 💌

---

and that's the whole page, bestie!! you now know literally everything this manpage is willing to tell you, which is a small amount of information delivered with maximum chaos. this was X Version 11, libxcb 1.17.0, and I'm obsessed with you for reading all of it 🎀💖 go forth and destroy some pixmaps (responsibly, through the proper XCB call, xcb_glx_destroy_pixmap, obviously). mwah! 🦋🌸💅