xcb_glx_destroy_context(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

πŸ’… NAME πŸ’…

xcb_glx_destroy_context β€” bestie, that's the whole name, that's it, that's the vibe (the original literally leaves the description blank, and we're being honest about it 🫢)


✨ SYNOPSIS ✨

First things first, you gotta pull in the header:

#include <xcb/glx.h>

🌸 Request function 🌸

xcb_void_cookie_t xcb_glx_destroy_context(xcb_connection_t *conn,
       xcb_glx_context_t context);

πŸŽ€ REQUEST ARGUMENTS πŸŽ€

  • conn β€” the XCB connection to X11. That's your link to the server, your group chat with the X server if you will πŸ’–
  • context β€” okay so. The original says TODO: NOT YET DOCUMENTED. and I'm not gonna lie to you and make something up, so. There it is. The manpage itself is out here with an unfinished thought 😭

πŸ¦‹ DESCRIPTION πŸ¦‹

Lowkey? There's nothing here. The original DESCRIPTION section is empty, no cap. The void. The silence. Not me staring at a blank paragraph πŸ’€


⭐ RETURN VALUE ⭐

It hands you back an xcb_void_cookie_t. And here's the tea: any errors (if there even are any) have to be handled in the event loop, bestie. That's the assignment.

But wait β€” if you'd rather handle errors directly with xcb_request_check instead, then you want xcb_glx_destroy_context_checked. Two doors, same hallway πŸšͺ✨ Head to xcb-requests(3) for the full details, iykyk.


🌈 ERRORS 🌈

This request does never generate any errors. Never ever. Zero. None. Iconic behaviour, honestly πŸ‘‘

πŸ’œ SEE ALSO πŸ’œ

Also empty in the original, so there's literally nothing to send you to. No links, no friends, just vibes 🧚


πŸ“ AUTHOR πŸ“

Generated from glx.xml. If you spot something wrong or wanna make it better, hit up xcb@lists.freedesktop.org for corrections and improvements πŸ’Œ


X Version 11 Β· libxcb 1.17.0 Β· xcb_glx_destroy_context(3)

That's the whole page, bestie β€” go destroy that context, slay πŸ’…βœ¨πŸ¦‹