xcb_glx_get_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

💖 xcb_glx_get_string 💖

okay so bestie, welcome to the xcb_glx_get_string(3) page — it's part of the XCB Requests squad, and yes, the NAME section of this one is literally just the function name and a lil dash with nothing after it. iconic minimalism honestly. no cap, that's the whole name.

✨ SYNOPSIS ✨

first things first, you gotta pull in the header:

#include <xcb/glx.h>

🌸 Request function 🌸

xcb_glx_get_string_cookie_t xcb_glx_get_string(xcb_connection_t *conn,
       xcb_glx_context_tag_t context_tag, uint32_t name);

🎀 Reply datastructure 🎀

here's the lil struct you get back, bestie — every field, no skips:

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

🦋 Reply function 🦋

xcb_glx_get_string_reply_t
       *xcb_glx_get_string_reply(xcb_connection_t *conn,
       xcb_glx_get_string_cookie_t cookie, xcb_generic_error_t **e);

⭐ Reply accessors ⭐

the lil helpers that dig stuff out of the reply for you:

char *xcb_glx_get_string_string(const xcb_glx_get_string_request_t
       *reply);

int xcb_glx_get_string_string_length(const xcb_glx_get_string_reply_t
       *reply);

xcb_generic_iterator_t xcb_glx_get_string_string_end(const
       xcb_glx_get_string_reply_t *reply);

💅 REQUEST ARGUMENTS 💅

  • conn — the XCB connection to X11. it's giving "your phone line to the server", fr.
  • context_tag — TODO: NOT YET DOCUMENTED. yeah bestie, the docs are ghosting us on this one, that's genuinely all it says, i'm not gonna make something up.
  • name — TODO: NOT YET DOCUMENTED. same situation, the original just shrugs here. 🙈

🌈 REPLY FIELDS 🌈

  • response_type — the type of this reply, which in this case is XCB_GLX_GET_STRING. this field also lives in the xcb_generic_reply_t, so you can use it to tell your replies apart from each other. very "which one of y'all texted me" energy.
  • sequence — the sequence number of the last request the X11 server processed. it's the receipt number of the group chat.
  • length — how long the reply is, in words. and just so we're clear, a word is 4 bytes. periodt.
  • n — TODO: NOT YET DOCUMENTED. yeah. again. the original really said "no thoughts, head empty" for this field. 😭

🌸 DESCRIPTION 🌸

okay so here's the thing — the DESCRIPTION section on this page is literally empty. not a single word. the original just put the heading there and dipped. i'm not about to invent lore, so: blank it is, bestie. 💀

🫶 RETURN VALUE 🫶

you get back an xcb_glx_get_string_cookie_t. that's your lil voucher, your "your order is being prepared" notification. 🍓

errors? those don't show up here — you handle them when you call the reply function xcb_glx_get_string_reply.

and if you'd rather catch errors in the event loop instead? use xcb_glx_get_string_unchecked. see xcb-requests(3) for the deets. iykyk.

🔥 ERRORS 🔥

this request does never generate any errors. not a one. zero drama, zero chaos, purely vibes. 💖

🌟 SEE ALSO 🌟

the original lists absolutely nothing here — no references, no cross-links, nothing. an empty section, main character energy, refusing to elaborate. ✨

👑 AUTHOR 👑

generated from glx.xml. if you wanna send corrections or improvements, hit up xcb@lists.freedesktop.org. they're accepting feedback, bestie, slide into those inboxes. 🎀

and that's a wrap on the whole page, fr fr — this one came from X Version 11, libxcb 1.17.0, and it's filed under xcb_glx_get_string(3). stay glxy, mwah 💅💖

📦 where this page comes from