xcb_glx_destroy_glx_pixmap(3)
π xcb_glx_destroy_glx_pixmap β the group chat rundown π
okay so bestie, this one lives in the xcb_glx family, which is the manual section 3 corner of the universe where we talk about GLX stuff over XCB. And listen β this page is short. Like, "texted you 'we need to talk' and then just said 'nvm'" short. But every crumb on it is sacred, so here we go. π«Ά
β¨ NAME β¨
xcb_glx_destroy_glx_pixmap β and that's literally it. No description. The manpage left it blank. She's mysterious. She's giving enigmatic icon. π
πΈ SYNOPSIS πΈ
First things first, you gotta pull in the header:
#include <xcb/glx.h>
π Request function
xcb_void_cookie_t xcb_glx_destroy_glx_pixmap(xcb_connection_t *conn,
xcb_glx_pixmap_t glx_pixmap);
Yes bestie, that's the whole signature. She returns an xcb_void_cookie_t and she takes two things. That's it. That's the vibe. β
π¦ REQUEST ARGUMENTS π¦
connβ the XCB connection to X11. Your lil pipeline to the X server, your main character link-up. Without it you're just a girl standing in front of a window system asking it to do things. πglx_pixmapβ okay so the original manpage saysTODO: NOT YET DOCUMENTED.and I'm not gonna lie to you and make something up, because making stuff up about a function that destroys a pixmap is exactly how you end up in the group chat asking "why is my pixmap gone". So: officially undocumented, bestie. π
π DESCRIPTION π
Nothing. Blank. Empty. The description section of this manpage is a void, which is honestly kind of on-brand for a function with void in its return type. No cap. π
π₯ RETURN VALUE π₯
She hands you back an xcb_void_cookie_t. And here's the important bit β errors (if any) have to be handled in the event loop. You don't get them handed to you at the door, you gotta go looking. π
But wait, there's another option: if you want to handle errors directly with xcb_request_check instead, use xcb_glx_destroy_glx_pixmap_checked. And for the full tea, see xcb-requests(3). π
π ERRORS π
This request does never generate any errors.
Read that again. Never. Not a single one. She is unbothered, she is flawless, she does not do drama. π§
π SEE ALSO π
Also blank. Nothing listed. The SEE ALSO section is out here with no friends. Not me feeling bad for a manpage section. π
π AUTHOR π
Generated from glx.xml. If you spot something wrong or want to improve it, hit up xcb@lists.freedesktop.org β they're the ones taking corrections and improvements. Be nice, be specific, include the receipts. π«Ά
and that's the whole page, bestie β short, sweet, and fully documented in the "we documented that we haven't documented it" way. β¨
X Version 11 πΈ libxcb 1.17.0 π xcb_glx_destroy_glx_pixmap(3) π and yes, we stanned every single empty section. periodt. π
π¦ where this page comes from
- alpine 3.22: libxcb-doc 1.17.0-r0 Β· MIT
- alpine 3.23: libxcb-doc 1.17.0-r1 Β· MIT
- alpine 3.24: libxcb-doc 1.17.0-r2 Β· MIT
- arch rolling: libxcb 1.17.0-1 Β· X11
- centos-stream 10: libxcb-devel 1.17.0-3.el10 Β· X11
- debian trixie: libxcb-doc 1.17.0-2
- fedora 43: libxcb-devel 1.17.0-6.fc43 Β· X11
- fedora 43: libxcb-devel 1.17.0-6.fc43 Β· X11
- fedora 44: libxcb-devel 1.17.0-7.fc44 Β· X11
- fedora 44: libxcb-devel 1.17.0-7.fc44 Β· X11
- nixpkgs unstable: libxcb 1.17.0
- opensuse-leap 16.0: libxcb-devel-doc 1.17.0-160000.2.2 Β· MIT
- ubuntu questing: libxcb-doc 1.17.0-2build1
- ubuntu resolute: libxcb-doc 1.17.0-2ubuntu1
- ubuntu stonking: libxcb-doc 1.17.0-2ubuntu1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms