xcb_xf86dri_destroy_context(3)

💅 NAME 💅

xcb_xf86dri_destroy_context — bestie, the NAME section of this manpage is literally just a dash. That's it. That's the whole name. The original authors left it blank and honestly? We respect the mystery. 🫶

✨ SYNOPSIS ✨

First things first, you gotta pull in the header:

#include <xcb/xf86dri.h>

🎀 Request function 🎀

xcb_void_cookie_t xcb_xf86dri_destroy_context(xcb_connection_t *conn,
       uint32_t screen, uint32_t context);

🌸 REQUEST ARGUMENTS 🌸

• conn — your XCB connection to X11. Your lil lifeline to the server, no cap. 💖
• screen — TODO: NOT YET DOCUMENTED. Yeah bestie, the docs said "we'll do it later" and then simply did not. 😭
• context — TODO: NOT YET DOCUMENTED. Same energy. The mystery continues. 🙈

🦋 DESCRIPTION 🦋

Okay so… there is genuinely nothing here. The DESCRIPTION section is empty. Not a crumb. Not a single sentence. The vibe is immaculate but the information is, and I say this with love, nonexistent. 💀

⭐ RETURN VALUE ⭐

It hands you back an xcb_void_cookie_t, periodt. Any errors (if there even are any) have to be handled over in the event loop, not right here in the moment.

But wait — if you'd rather deal with errors directly, using xcb_request_check, then you want xcb_xf86dri_destroy_context_checked instead. Head over to xcb-requests(3) for the full tea. 👑

🌈 ERRORS 🌈

This request does never generate any errors. Zero. None. Clean slate, flawless, not one single problem. Slay. 💅

🔥 SEE ALSO 🔥

Nothing here either bestie, the SEE ALSO section is giving empty-plate-at-the-function energy. 🍓

💜 AUTHOR 💜

Generated from xf86dri.xml. If you spot something wrong and wanna help a girl out, contact xcb@lists.freedesktop.org for corrections and improvements. iykyk. 🧚

And that's the whole page, babe! This masterpiece came to you courtesy of X Version 11 and libxcb 1.17.0 — go forth, destroy those contexts, and stay iconic. 💅✨🎀