XCB_RANDR_SET_PROVIDER_OFFLOAD_SINK_CHECKED(3)
π xcb_randr_set_provider_offload_sink β the manual page bestie
okay so this is a page from the XCB Requests corner of the libxcb world, and it's giving very niche, very "iykyk" energy. It lives in xcb_randr_set_provider_offload_sink(3) and it is, no cap, one of the shortest manpages you will ever meet. Let's get into it. π
β¨ NAME β¨
xcb_randr_set_provider_offload_sink β and that's literally it, the original page just leaves a lil dash hanging there with nothing after it. The name is the whole personality. π
πΈ SYNOPSIS πΈ
First things first, you gotta pull in the header:
#include <xcb/randr.h>
π¦ Request function π¦
here's the signature, copy it exactly bestie, no improvising:
xcb_void_cookie_t
xcb_randr_set_provider_offload_sink(xcb_connection_t *conn,
xcb_randr_provider_t provider,
xcb_randr_provider_t sink_provider,
xcb_timestamp_t config_timestamp);
note the return type: it's an xcb_void_cookie_t. remember that, it comes back later. β
π REQUEST ARGUMENTS π
Four args, four lil besties, and the docs are... not forthcoming. We report faithfully, periodt:
connβ the XCB connection to X11. this one actually got documented, slay. π₯providerβTODO: NOT YET DOCUMENTED.yeah. that's the whole thing. the manpage said what it said. πsink_providerβTODO: NOT YET DOCUMENTED.again. iconic in a cursed way.config_timestampβTODO: NOT YET DOCUMENTED.three for three, the author really said "figure it out" π
okay but fr fr β those TODO: NOT YET DOCUMENTED. lines are verbatim from the original, so don't come for me, I'm just the messenger. π«Ά
π DESCRIPTION π
There is a DESCRIPTION heading. Under it? Nothing. Empty. Void. Main character silence. The section exists purely as a vibe. β¨
π RETURN VALUE π
okay so this is the part that actually tells you something, so listen up:
It returns an xcb_void_cookie_t. That means errors (if any) have to be handled in the event loop β you don't get them handed to you right here, you gotta go catch them yourself later. π
If you'd rather handle errors directly with xcb_request_check instead, then use xcb_randr_set_provider_offload_sink_checked. See xcb-requests(3) for the details, bestie, that's where the whole story lives. π§
π₯ ERRORS π₯
short and sweet and honestly a little slay:
This request does never generate any errors.
that's it. that's the section. no errors, no drama, no stress. we love a low-maintenance request. π
π SEE ALSO π
nothing listed. the SEE ALSO section is standing there in an empty room, looking cute. πΈ
π AUTHOR π
Generated from randr.xml. Contact xcb@lists.freedesktop.org for corrections and improvements. so if you spot something weird, that's your email, go be the change you wish to see in the manpage. π§
and that's the whole page, bestie. short, mysterious, three TODOs deep. obsessed, honestly. π¦
sign-off szn: this page comes to you from X Version 11, with libxcb 1.17.0 doing the heavy lifting β mwah, take care of her, and go read xcb-requests(3) if you want the full tea. πβ¨π
π¦ where this page comes from
- alpine 3.22: libxcb-doc 1.17.0-r0 Β· MIT
- alpine 3.23: libxcb-doc 1.17.0-r1 Β· MIT
- alpine 3.24: libxcb-doc 1.17.0-r2 Β· MIT
- arch rolling: libxcb 1.17.0-1 Β· X11
- centos-stream 10: libxcb-devel 1.17.0-3.el10 Β· X11
- debian trixie: libxcb-doc 1.17.0-2
- fedora 43: libxcb-devel 1.17.0-6.fc43 Β· X11
- fedora 43: libxcb-devel 1.17.0-6.fc43 Β· X11
- fedora 44: libxcb-devel 1.17.0-7.fc44 Β· X11
- fedora 44: libxcb-devel 1.17.0-7.fc44 Β· X11
- nixpkgs unstable: libxcb 1.17.0
- opensuse-leap 16.0: libxcb-devel-doc 1.17.0-160000.2.2 Β· MIT
- ubuntu questing: libxcb-doc 1.17.0-2build1
- ubuntu resolute: libxcb-doc 1.17.0-2ubuntu1
- ubuntu stonking: libxcb-doc 1.17.0-2ubuntu1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms