xcb_xfixes_change_cursor(3)
β¨ NAME β¨
xcb_xfixes_change_cursor β bestie, the name section literally gave us nothing, no description, zero, nada π so we're just gonna say it: it's an XCB request from the XFixes extension, it's called xcb_xfixes_change_cursor, and the rest of this page is us finding out together π«Ά
πΈ SYNOPSIS πΈ
First things first, you gotta pull in the header, okay?
#include <xcb/xfixes.h>
π Request function
xcb_void_cookie_t xcb_xfixes_change_cursor(xcb_connection_t *conn,
xcb_cursor_t source, xcb_cursor_t destination);
That's the whole signature, no cap. Three args, one cookie back. πͺ
π¦ REQUEST ARGUMENTS π¦
connβ the XCB connection to X11, aka your lil hotline to the display server. Everything goes through her πsourceβ TODO: NOT YET DOCUMENTED. likeβ¦ the manpage really said "figure it out" πdestinationβ TODO: NOT YET DOCUMENTED. same energy, same void, same unanswered question π
Not me being unable to tell you whatsourceanddestinationactually do β because the docs literally sayTODO: NOT YET DOCUMENTED.I'm not making that up, bestie, that's verbatim what's in the source. We stay honest in this house π
π DESCRIPTION π
Okay soβ¦ there is no description. The section exists. It is empty. It's giving "the group chat went quiet" energy π We're keeping the heading because the structure matters, but the vibes inside are just silence and vibes.
β RETURN VALUE β
You get back an xcb_void_cookie_t, which is the "no actual data, but here's your receipt" cookie. Any errors? They do not come back to you here β you gotta handle them in the event loop, fr fr π₯
But wait, there's another route: if you'd rather handle errors directly, use xcb_request_check instead of vibing with the cookie. In that case you want the checked version:
xcb_xfixes_change_cursor_checkedβ the one you pair withxcb_request_check.
All the deets live in xcb-requests(3), go read her π
π ERRORS π
This request does never generate any errors. Never. Not once. Not ever. Iconic behaviour honestly, the reliability is unmatched π β¨
π§ SEE ALSO π§
Nothing here. Empty. The SEE ALSO section is a ghost town and we're respecting her privacy π
π AUTHOR π
Generated from xfixes.xml. If something's wrong or you wanna improve it, hit up xcb@lists.freedesktop.org β they handle corrections and improvements, and they're the ones to tell, not me π«Ά
And that's the whole page, bestie!! π This lil cutie came from X Version 11, libxcb 1.17.0, and yes the manual page is literally titled xcb_xfixes_change_cursor(3) β take care of her, she's doing her best out here πβ¨π¦
π¦ 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