xcb_glx_is_query_arb(3)
π xcb_glx_is_query_arb β from the XCB Requests girlies (section 3 of your manual, bestie)
okay so real talk, this is a page straight out of libxcb's GLX corner, and it's one of those ones where the docs are like... a little mysterious. We're gonna walk through it together though, no cap. π¦
β¨ NAME β¨
xcb_glx_is_query_arb β and honestly? The original page leaves the description blank, so there is literally nothing written here. Iconic of it, honestly. π«Ά
πΈ SYNOPSIS πΈ
First things first, you gotta pull in the header:
#include <xcb/glx.h>
π Request function π
xcb_glx_is_query_arb_cookie_t
xcb_glx_is_query_arb(xcb_connection_t *conn,
xcb_glx_context_tag_t context_tag, uint32_t id);
π Reply datastructure π
typedef struct xcb_glx_is_query_arb_reply_t {
uint8_t response_type;
uint8_t pad0;
uint16_t sequence;
uint32_t length;
xcb_glx_bool32_t ret_val;
} xcb_glx_is_query_arb_reply_t;
π Reply function π
xcb_glx_is_query_arb_reply_t
*xcb_glx_is_query_arb_reply(xcb_connection_t *conn,
xcb_glx_is_query_arb_cookie_t cookie, xcb_generic_error_t **e);
π REQUEST ARGUMENTS π
connβ the XCB connection to X11. your lil lifeline to the server, periodt. π«context_tagβ TODO: NOT YET DOCUMENTED. yeah bestie, that's all we got. the mystery is part of the charm. πidβ TODO: NOT YET DOCUMENTED. also a mystery. we move. π
π REPLY FIELDS π
response_typeβ the type of this reply. In this case it'sXCB_GLX_IS_QUERY_ARB. This field is also chillin' insidexcb_generic_reply_t, and it's how you tell your replies apart from each other. v important, don't skip it. πsequenceβ the sequence number of the last request the X11 server processed. it's giving receipt. π§Ύlengthβ how long the reply is, in words. and reminder bestie: a word is 4 bytes. β¨ret_valβ TODO: NOT YET DOCUMENTED. the plot thickens. π
π DESCRIPTION π
So... the original page has this heading and then absolutely nothing under it. An empty section. A void. The main character energy of just not explaining yourself. π
β RETURN VALUE β
It hands you back an xcb_glx_is_query_arb_cookie_t. πͺ
Errors? You handle those when you call the reply function, xcb_glx_is_query_arb_reply.
But wait β if you'd rather deal with errors in the event loop instead, use xcb_glx_is_query_arb_unchecked. See xcb-requests(3) for the deets. π
π₯ ERRORS π₯
This request never generates any errors. Ever. Zero. None. It's the chillest request in the group chat. π§
π¦ SEE ALSO π¦
Yeah so... there's nothing listed here. No cross-references. Just vibes. If you were hoping for a friend to click through to, sorry bestie, it's just you and this page. π
π AUTHOR π
Generated from glx.xml. Contact xcb@lists.freedesktop.org for corrections and improvements. (So if something's wrong, that's the group chat to slide into. they're nice, I promise. π«Ά)
ok that's the whole page, you ate that π go forth and query, or whatever this does once someone documents it. πΈ
X Version 11 β’ libxcb 1.17.0 β’ xoxo, your favorite manual page πβ¨
π¦ 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