xcb_glx_destroy_pbuffer(3)
β¨ xcb_glx_destroy_pbuffer β¨
okay bestie, so this one lives in the XCB Requests manual section, and it's a request function from libxcb β specifically the GLX-flavoured corner of it. Yes, that 3 in the name means it's a library call, iykyk. π
πΈ NAME πΈ
xcb_glx_destroy_pbuffer β the request that destroys a GLX pbuffer π
(the original page left the one-liner blank, so we're all just vibing with the function name here)
π¦ SYNOPSIS π¦
#include <xcb/glx.h>
Request function
xcb_void_cookie_t xcb_glx_destroy_pbuffer(xcb_connection_t *conn,
xcb_glx_pbuffer_t pbuffer);
π REQUEST ARGUMENTS π
connβ the XCB connection to X11. your lil hotline to the display server, fr fr πpbufferβTODO: NOT YET DOCUMENTED.π yes literally, the original says that. not me adding lore that isn't there β we're keeping it exactly as-is. π«Ά
π DESCRIPTION π
soooooβ¦ the original page has an empty DESCRIPTION section. nothing. void. silence. π the description is giving absolutely nothing, and we are not about to invent behaviour that isn't documented, bestie. no cap.
what we do know: it's a request function, it takes a connection and a pbuffer, and it hands you back a cookie. that's the whole vibe. π
π₯ RETURN VALUE π₯
It returns an xcb_void_cookie_t. π
Errors (if any) have to be handled in the event loop β that's the whole deal with void cookies, they don't hand you the receipts on the spot.
If you'd rather handle errors directly with xcb_request_check instead, use xcb_glx_destroy_pbuffer_checked. see xcb-requests(3) for the details, periodt. β¨
π ERRORS π
This request does never generate any errors. iconic behaviour honestly. zero drama, zero mess. π§
not a single error. not one. she simply does not miss. π
π SEE ALSO π
(empty in the original β nothing listed, nothing to link, we respect the silence π)
π AUTHOR π
Generated from glx.xml. Contact xcb@lists.freedesktop.org for corrections and improvements. π
and that's the whole page, bestie!! π this was generated from glx.xml, part of X Version 11, shipped in libxcb 1.17.0, and it's the xcb_glx_destroy_pbuffer(3) page. go forth and destroy those pbuffers responsibly. mwah. π«Άβ¨
π¦ 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