xcb_glx_destroy_glx_pixmap(3)

πŸ“¦
version 1.17.0 Β· 4 versions
, in alpine 3.22, alpine 3.23, alpine 3.24, arch rolling, centos-stream 10, debian trixie, fedora 43, fedora 44, nixpkgs unstable, opensuse-leap 16.0, ubuntu questing, ubuntu resolute, ubuntu stonking

πŸ’– 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 says TODO: 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. πŸ’