xcb_render_add_glyphs(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_render_add_glyphs β€” the manual page bestie πŸ’–

okay so this is the xcb_render_add_glyphs(3) page from the XCB Requests manual, and we're gonna get through it together, no cap. it's a request function, it lives in libxcb, and it's literally one of those "add glyphs to a glyphset" situations. let's go πŸ¦‹


🌸 NAME 🌸

xcb_render_add_glyphs β€”

(yes bestie, the original really does just leave it hanging like that. the description is vibing, not existing. we move on πŸ’…)


✨ SYNOPSIS ✨

first things first, you gotta pull in the header:

#include <xcb/render.h>

πŸŽ€ Request function πŸŽ€

here's the whole signature, character for character, don't @ me:

xcb_void_cookie_t xcb_render_add_glyphs(xcb_connection_t *conn,
       xcb_render_glyphset_t glyphset, uint32_t glyphs_len, const
       uint32_t *glyphids, const xcb_render_glyphinfo_t *glyphs,
       uint32_t data_len, const uint8_t *data);

that's a lot of parameters and honestly? it's giving "trust the process" πŸ”₯


πŸ’œ REQUEST ARGUMENTS πŸ’œ

every single one, in order, no skipping, periodt:

  • conn β€” the XCB connection to X11. your lil lifeline to the server, your main character connection 🫢
  • glyphset β€” TODO: NOT YET DOCUMENTED.
  • glyphs_len β€” TODO: NOT YET DOCUMENTED.
  • glyphids β€” TODO: NOT YET DOCUMENTED.
  • glyphs β€” TODO: NOT YET DOCUMENTED.
  • data_len β€” TODO: NOT YET DOCUMENTED.
  • data β€” TODO: NOT YET DOCUMENTED.
ngl the docs team left six of these on read 😭 that's not me being shady, that's just literally what the page says. TODO: NOT YET DOCUMENTED. iconic in a cursed way πŸ’€

🌈 DESCRIPTION 🌈

...and that's it. that's the whole description section. it's empty. it's giving minimalist. it's giving "we'll fill this in later" πŸ™ˆ

the original has literally nothing here, so i'm not gonna make anything up β€” that would be lying to my bestie and i would never πŸ’–


⭐ RETURN VALUE ⭐

so it hands you back an xcb_void_cookie_t. and because it's a void cookie, any errors (if there even are any) have to be handled over in the event loop, not right here, bestie. that's just the deal πŸ¦‹

but wait β€” if you wanna handle errors directly instead of waiting around in the event loop, you can use xcb_request_check. and for that you want the checked version of this request: xcb_render_add_glyphs_checked. all the deets on how that works live in xcb-requests(3). go read it, i'll wait πŸ’…


πŸ’€ ERRORS πŸ’€

this request does never generate any errors.

literally zero. none. not a single one. it's the chillest request at the function and it did NOT come to start drama πŸŽ€


πŸ‘‘ SEE ALSO πŸ‘‘

nothing here either β€” the original just has the heading and then vibes. so: no see-also entries. that's the whole tea β˜•


🌸 AUTHOR 🌸

this page was generated from render.xml. if you spot something wrong or wanna send corrections and improvements, hit up xcb@lists.freedesktop.org β€” they're accepting notes, fr fr 🫢


and that's the whole page bestie!! this came from X Version 11, libxcb 1.17.0, and the page is xcb_render_add_glyphs(3) in case you scrolled all the way down here and forgot what we were even reading. slay, go forth, add those glyphs βœ¨πŸ’–