xcb_glx_client_info(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_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. πŸ’–βœ¨πŸ¦‹πŸŒΈπŸ’…πŸ«ΆπŸ‘‘