xcb_glx_query_server_string(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_query_server_string β€” bestie, the description slot on this one is literally empty, like an unanswered text at 3am. That's it, that's the name, we move πŸ’…


🌈 SYNOPSIS

🫢 Request function

#include <xcb/glx.h>

xcb_glx_query_server_string_cookie_t
       xcb_glx_query_server_string(xcb_connection_t *conn,
       uint32_t screen, uint32_t name);

πŸŽ€ Reply datastructure

typedef struct xcb_glx_query_server_string_reply_t {
    uint8_t  response_type;
    uint8_t  pad0;
    uint16_t sequence;
    uint32_t length;
    uint8_t  pad1[4];
    uint32_t str_len;
    uint8_t  pad2[16];
} xcb_glx_query_server_string_reply_t;

πŸ’– Reply function

xcb_glx_query_server_string_reply_t
       *xcb_glx_query_server_string_reply(xcb_connection_t *conn,
       xcb_glx_query_server_string_cookie_t cookie,
       xcb_generic_error_t **e);

πŸ¦‹ Reply accessors

char *xcb_glx_query_server_string_string(const
       xcb_glx_query_server_string_request_t *reply);

int xcb_glx_query_server_string_string_length(const
       xcb_glx_query_server_string_reply_t *reply);

xcb_generic_iterator_t xcb_glx_query_server_string_string_end(const
       xcb_glx_query_server_string_reply_t *reply);

🌸 REQUEST ARGUMENTS 🌸

  • conn β€” your XCB connection to X11, the ride-or-die that carries every request. no conn, no vibes ✨
  • screen β€” TODO: NOT YET DOCUMENTED. yeah bestie the docs said "later" and later never came 😭
  • name β€” TODO: NOT YET DOCUMENTED. same energy, same empty page, we stay strong 🫢

πŸ’œ REPLY FIELDS πŸ’œ

  • response_type β€” the type of this reply, and in this case it's XCB_GLX_QUERY_SERVER_STRING. this field is also chillin' inside xcb_generic_reply_t, so you can use it to tell your replies apart from each other. it's giving name tag at a party πŸŽ€
  • sequence β€” the sequence number of the last request the X11 server actually processed. the receipt, basically 🧾
  • length β€” how long the reply is, measured in words (and a word is 4 bytes, keep that in your notes πŸ“).
  • str_len β€” TODO: NOT YET DOCUMENTED. the mystery member of the struct, we love an enigma πŸ’€

πŸ“ DESCRIPTION πŸ“

Okay so… there is genuinely nothing here. Like, the original page has the heading and then silence. Empty. A void. Main character with no lines πŸ™ˆ We're not inventing lore that isn't there, so consider this your official vibe check: no description, no cap.


⭐ RETURN VALUE ⭐

You get back an xcb_glx_query_server_string_cookie_t. Adorable. But listen β€” errors have to be handled when you call the reply function xcb_glx_query_server_string_reply.

If you'd rather handle errors in the event loop instead (very valid, very ✨organized✨ of you), use xcb_glx_query_server_string_unchecked. Head over to xcb-requests(3) for the full tea β˜•


πŸ”₯ ERRORS πŸ”₯

This request does never generate any errors. literally never. zero drama, zero chaos, an absolute angel πŸ‘‘ no xcb_generic_error_t jumpscares for you, bestie.

πŸ‘‘ SEE ALSO πŸ‘‘

Nothing listed here β€” the SEE ALSO section is as empty as my schedule on a Sunday 🌈


🌸 AUTHOR 🌸

Generated from glx.xml. If you spot something wrong or wanna make it better, contact xcb@lists.freedesktop.org β€” they're taking corrections and improvements, and honestly? slay for that 🫢


okay that's the whole page, you made it to the end, iconic behavior honestly. This one came to you from X Version 11 and libxcb 1.17.0 β€” go forth and query those server strings, bestie πŸ’–βœ¨πŸŽ€πŸ¦‹