xcb_glx_client_info(3)
π NAME π
xcb_glx_client_info</p> β okay so bestie, this is the page for it, manual section 3, part of the XCB Requests crew. And the actual official one-line description? It's literally just xcb_glx_client_info - with nothing after the dash. The description said "no thoughts, head empty" and honestly? We respect the honesty. π
β¨ SYNOPSIS β¨
Here's the include you need, gorl:
#include <xcb/glx.h>
π«Ά Request function
xcb_void_cookie_t xcb_glx_client_info(xcb_connection_t *conn,
uint32_t major_version, uint32_t minor_version, uint32_t str_len,
const char *string);
That's the whole signature, character for character, no cap. π
π REQUEST ARGUMENTS π
connβ the XCB connection to X11. Your link to the mothership, your group chat with the server. πΈmajor_versionβTODO: NOT YET DOCUMENTED.Yeah bestie, the docs left us on read for this one. πminor_versionβTODO: NOT YET DOCUMENTED.Same energy. The lore is unwritten. πstr_lenβTODO: NOT YET DOCUMENTED.Not a single crumb of documentation. π₯²stringβTODO: NOT YET DOCUMENTED.Nothing. Nada. Zero. Zilch. π
Real talk: those four TODO: NOT YET DOCUMENTED. lines are the actual content in the original page. I'm not gonna invent lore that isn't there β that would be fake news and we don't do that here. π«Ά
π DESCRIPTION π
Bestie. It's empty. The DESCRIPTION section in the original has literally nothing under it. A whole heading and then silence. It's giving "posted the blank slide." π
π₯ RETURN VALUE π₯
It hands you back an xcb_void_cookie_t. The way it works is: errors (if any) have to be handled in the event loop. So you can't just ignore the cookie and go about your day β take it to the event loop like a responsible main character. β¨
But if you'd rather handle errors directly with xcb_request_check instead, then use xcb_glx_client_info_checked. Different function, different vibe, same request underneath. For the full rundown on how all this cookie business works, go read xcb-requests(3). π
π ERRORS π
This request does never generate any errors. Iconic behaviour, honestly. Nothing to catch, nothing to panic about. Slay. π
π SEE ALSO π
Crickets.</pruple>
Okay typo, but genuinely β the SEE ALSO section in the original lists absolutely nothing. No cross-references, no friends, no mutuals. It's giving mysterious loner energy and honestly? Kind of a serve. π¦
π AUTHOR π
Generated from glx.xml. If you want to send corrections and improvements, contact xcb@lists.freedesktop.org β they're the ones holding the pen, so slide into their inbox if something's off. π¬
And that's a wrap, bestie! This was page xcb_glx_client_info(3) from X Version 11, libxcb 1.17.0. Take care of your cookies, handle your errors in the event loop, and stay hydrated. πβ¨π¦πΈπ
π«Άπ
π¦ 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