xcb_composite...m_border_clip(3)
π¦ NAME π¦
okay bestie, say hi to xcb_composite_create_region_from_border_clip π
that's it. that's the name. the description slot? literally empty. the manpage said nothing and honestly it meant it. no cap. π
it lives in the XCB Requests corner of the manual, section 3, and the page header up top is truncating the name to xcb_composite...m_border_clip(3) because even man was like "girl this name is long" π
β¨ SYNOPSIS β¨
first you gotta bring the header in, or nothing works:
#include <xcb/composite.h>
then, the request function herself π:
xcb_void_cookie_t
xcb_composite_create_region_from_border_clip(xcb_connection_t *conn,
xcb_xfixes_region_t region, xcb_window_t window);
she returns an xcb_void_cookie_t and takes three little besties. we'll meet them in a sec π«Ά
πΈ REQUEST ARGUMENTS πΈ
connβ the XCB connection to X11. your little lifeline to the server, the group chat you're actually sending messages in πregionβTODO: NOT YET DOCUMENTED.yeah. the docs said "we'll do it later" and then never did. iconic behaviour, honestly πwindowβTODO: NOT YET DOCUMENTED.same energy. same void. no notes. π
not me reading the docs hoping for lore and getting two TODOs in a trench coat π i'm just the messenger bestie, i'm not gonna make stuff up for you.
π DESCRIPTION π
soβ¦ there isn't one. the DESCRIPTION section on this page is empty. completely. the way that the original manpage just has the heading and then absolute silence? it's giving "ghosted" π«₯
i'm not gonna invent lore that isn't there, so: nothing to see, moving on, periodt.
π RETURN VALUE π
she hands you back an xcb_void_cookie_t. that's the vibe. β¨
now listen, because this part matters: errors (if any) have to be handled in the event loop. like, you don't get them thrown at you immediately, you go collect them later like a little package at the front desk π¦
if you'd rather handle errors directly with xcb_request_check instead, then use xcb_composite_create_region_from_border_clip_checked β that's the checked version, she's the one who'll actually tell you what went wrong π«Ά
and for all the details, go read xcb-requests(3). iykyk.
π ERRORS π
this request does never generate any errors. fr fr. she's a good girl, she causes no drama, zero chaos, no smoke π
so if something IS breaking, bestie, it's not her. look elsewhere. π
π SEE ALSO π
nothing here either π the SEE ALSO section is empty on this page β no references, no cross-links, just vibes and open space. so cute, so unhelpful, we move π
π AUTHOR π
this page was generated from composite.xml. if you've got corrections or improvements, hit up xcb@lists.freedesktop.org β they're the ones who actually want your feedback, not me, i'm just the hype girl π
okay so real talk, this page is short and the docs are shy, but you got this bestie β go make that border clip region, slay, and remember: cookie now, errors later πβ¨
signing off from X Version 11, running libxcb 1.17.0, same energy as the footer that brought you here π¦ mwah π
π¦ 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