xcb_glx_finish(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_finish β€” the XCB Requests glow-up

okay bestie, so this is xcb_glx_finish(3), living its best life over in the XCB Requests section of the manual. she's a libxcb girlie. let's get into it 🫢


✨ NAME ✨

xcb_glx_finish β€” literally that's it, the name section is just vibes and the function name (the original has a lil dash and then nothing, and honestly? iconic. no notes.)


πŸ¦‹ SYNOPSIS πŸ¦‹

first things first, you gotta pull in the header:

#include <xcb/glx.h>

🌸 Request function 🌸

xcb_glx_finish_cookie_t xcb_glx_finish(xcb_connection_t *conn,
       xcb_glx_context_tag_t context_tag);

πŸŽ€ Reply datastructure πŸŽ€

this is the lil struct that comes back at you:

typedef struct xcb_glx_finish_reply_t {
    uint8_t  response_type;
    uint8_t  pad0;
    uint16_t sequence;
    uint32_t length;
} xcb_glx_finish_reply_t;

⭐ Reply function ⭐

and here's how you actually go get that reply:

xcb_glx_finish_reply_t *xcb_glx_finish_reply(xcb_connection_t *conn,
       xcb_glx_finish_cookie_t cookie, xcb_generic_error_t **e);

πŸ’œ REQUEST ARGUMENTS πŸ’œ

  • conn β€” the XCB connection to X11. your lil phone line to the server, fr fr.
  • context_tag β€” TODO: NOT YET DOCUMENTED. yeah bestie, the docs said "we'll finish this later" and then never did 😭 we simply do not know. moving on!

🌈 REPLY FIELDS 🌈

  • response_type β€” what kind of reply this is. in this case it's XCB_GLX_FINISH. this field is also chillin' inside xcb_generic_reply_t, so you can use it to tell your replies apart from each other when you've got a whole pile of them.
  • sequence β€” the sequence number of the last request the X11 server processed. it's giving "receipt number" energy 🧾
  • length β€” how long the reply is, in words. and a word, bestie, is 4 bytes. remember that. it will come up.

πŸ‘‘ DESCRIPTION πŸ‘‘

so… the original page's DESCRIPTION section is empty. like, genuinely empty. nothing. zero. a void. we're not making anything up here because that would be lying, and lying is not the move. so: it's blank, and that's canon. πŸ™ˆ


πŸ”₯ RETURN VALUE πŸ”₯

she returns an xcb_glx_finish_cookie_t. and listen β€” errors do NOT get handled here. you handle them when you call the reply function xcb_glx_finish_reply.

but if you'd rather handle your errors in the event loop instead? use xcb_glx_finish_unchecked for that. see xcb-requests(3) for the full tea. β˜•


πŸ’€ ERRORS πŸ’€

This request does never generate any errors.

that's right. no errors. not a single one. she's flawless. πŸ’…βœ¨


πŸ“ SEE ALSO πŸ“

(the original lists nothing here, so… nothing here it is! consider this section a peaceful little meadow 🌸)


🫢 AUTHOR 🫢

Generated from glx.xml. for corrections and improvements, hit up xcb@lists.freedesktop.org. πŸ“§


and that's the whole page, bestie!! X Version 11, libxcb 1.17.0, and this page is xcb_glx_finish(3) β€” go forth and finish those GLX things πŸ’–πŸŽ€πŸ¦‹ slay!