xcb_xfixes_region_extents(3)
π xcb_xfixes_region_extents π
okay bestie, so this one lives in the xcb family β specifically the XFixes extension β and it's a request function, meaning you're sending a request to the X server and getting a cookie back. The manpage is, and I say this with love, extremely sparse. Like, it's giving "we wrote the synopsis and then went to get boba." But we're gonna cover every crumb it gives us. π
β¨ NAME β¨
xcb_xfixes_region_extents β and that's it. The description field is literally blank in the original, so I'm not gonna make one up for you. (iykyk)
πΈ SYNOPSIS πΈ
First, you gotta pull in the header:
#include <xcb/xfixes.h>
π Request function π
xcb_void_cookie_t xcb_xfixes_region_extents(xcb_connection_t *conn,
xcb_xfixes_region_t source, xcb_xfixes_region_t destination);
See that xcb_void_cookie_t return type? Yeah β it hands you back a cookie and no data. You deal with any errors later, in the event loop. More on that below. π
π¦ REQUEST ARGUMENTS π¦
connβ the XCB connection to X11. Your link to the server, your main character, the whole vibe. π₯sourceβ TODO: NOT YET DOCUMENTED. yeah. that's the actual text. the docs simply did not show up. πdestinationβ also TODO: NOT YET DOCUMENTED. same energy. bestie, the documentation for these two is not serving. I refuse to invent behaviour that isn't in the page, so this is genuinely all we get. π
Real talk: if you need to know whatsourceanddestinationactually do here, the manpage is not gonna tell you. That's a "go read the source / the XML" situation, fr fr.
π DESCRIPTION π
So... this section is empty in the original. Completely. Nothing. Not a single word. π«Ά
I'm not gonna fill it with guesses, because guessing at X protocol behaviour is how you end up debugging at 3am. The section exists, it's just got nothing in it. Iconic in a "the audacity" kind of way. β¨
β RETURN VALUE β
You get an xcb_void_cookie_t back. Errors β if there are any β have to be handled in the event loop. That's the deal.
If you'd rather check for errors directly, right there, no event loop involved, use:
xcb_xfixes_region_extents_checked
instead. That's the checked variant. For all the deets on how that works, go see xcb-requests(3). π
π ERRORS π
This request never generates any errors. Clean. No drama. No error codes to catch. We love a low-maintenance request. π
πΈ SEE ALSO πΈ
Nothing listed here in the original β the section is empty. So there's nothing to send you off to. No links, no friends, just vibes. π¦
π AUTHOR π
Generated from xfixes.xml. If you spot something wrong or wanna make it better, contact xcb@lists.freedesktop.org for corrections and improvements. They're the ones to @ basically. π§
And that's the whole page, bestie. Short, sweet, and 90% TODO. Not my fault, I'm just the messenger. ππ
X Version 11 Β· libxcb 1.17.0 Β· xcb_xfixes_region_extents(3) β mwah, take care of her, she's doing her best πβ¨π
π¦ 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