xcb_record_create_context(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_record_create_context(3) πŸ’–

okay bestie, so this one lives in the XCB Requests corner of the manual, and it's genuinely so niche but we're gonna get through it together, no cap. it's giving "the docs said TODO and meant it" energy but that's fine, we ball. πŸŽ€


🌸 NAME 🌸

xcb_record_create_context β€” bestie the description is literally empty (the original page left it blank, so we're not gonna invent one, periodt)


✨ SYNOPSIS ✨

grab the header first, always:

#include <xcb/record.h>

Request function β€” the main character function itself:

xcb_void_cookie_t xcb_record_create_context(xcb_connection_t *conn,
       xcb_record_context_t context,
       xcb_record_element_header_t element_header,
       uint32_t num_client_specs, uint32_t num_ranges, const
       xcb_record_client_spec_t *client_specs, const
       xcb_record_range_t *ranges);
yes the line breaks are cursed, that's just how C declarations behave when they get formatted for a manpage. iconic of them honestly. πŸ’…

πŸ¦‹ REQUEST ARGUMENTS πŸ¦‹

  • conn β€” the XCB connection to X11. your lil phone line to the X server, if you will. πŸ“ž
  • context β€” TODO: NOT YET DOCUMENTED. 🫠 (not me, the actual manpage. i'm just the messenger.)
  • element_header β€” TODO: NOT YET DOCUMENTED. 🫠
  • num_client_specs β€” TODO: NOT YET DOCUMENTED. 🫠
  • num_ranges β€” TODO: NOT YET DOCUMENTED. 🫠
  • client_specs β€” TODO: NOT YET DOCUMENTED. 🫠
  • ranges β€” TODO: NOT YET DOCUMENTED. 🫠

πŸ’œ DESCRIPTION πŸ’œ

so... the DESCRIPTION section on this page is completely empty. nothing. void. the manpage equivalent of leaving you on read. 😭 we don't make stuff up around here though, so we're just gonna sit with that and respect it. πŸ§˜β€β™€οΈ


πŸ‘‘ RETURN VALUE πŸ‘‘

it hands you back an xcb_void_cookie_t. and here's the tea β€” any errors (if any even show up) have to be handled in the event loop. like, you don't get them handed to you directly, you gotta go get them. πŸ”₯

if you're the type who wants errors directly instead, with xcb_request_check, then use xcb_record_create_context_checked instead. see xcb-requests(3) for the details, bestie. πŸ“š


πŸ’€ ERRORS πŸ’€

this request never generates any errors. not one. zero. a clean sheet. slay. ✨


πŸŽ€ SEE ALSO πŸŽ€

nothing here, bestie. the original SEE ALSO section is empty, so there's nothing to point you at. we're not adding anything that wasn't there, no cap. πŸ™ˆ

πŸ’… AUTHOR πŸ’…

Generated from record.xml. Contact xcb@lists.freedesktop.org for corrections and improvements. 🫢


sign-off time 🌈

this page came from X Version 11, libxcb 1.17.0, and it's filed under xcb_record_create_context(3). that's the whole vibe, bestie β€” go forth and create contexts or whatever. mwah. πŸ’–πŸ’…βœ¨