xcb_xfixes_ch...ursor_by_name(3)
π xcb_xfixes_change_cursor_by_name β bestie edition π
okay so welcome to the xcb_xfixes_ch...ursor_by_name(3) page, part of the XCB Requests family, and yes the title in the header is literally truncated with dots like that, that's just how the man page gods named it, we don't ask questions π
β¨ NAME β¨
xcb_xfixes_change_cursor_by_name β and that's it. no little dash-description after it. the original page just left that part blank, so we're leaving it blank too. iconic mystery behaviour, honestly π
π¦ SYNOPSIS π¦
first, the include, because you can't slay what you can't #include:
#include <xcb/xfixes.h
wait no. it's this, exactly this:
#include <xcb/xfixes.h>
then, the request function itself:
xcb_void_cookie_t
xcb_xfixes_change_cursor_by_name(xcb_connection_t *conn,
xcb_cursor_t src, uint16_t nbytes, const char *name);
πΈ REQUEST ARGUMENTS πΈ
connβ the XCB connection to X11. your lil pipeline to the X server, your main character link, the whole vibe π«Άsrcβ TODO: NOT YET DOCUMENTED. yeah. the docs said "not yet". we're passing that energy straight through, no cap πnbytesβ also TODO: NOT YET DOCUMENTED. πnameβ and also TODO: NOT YET DOCUMENTED. bestie the entire argument list is a mystery box and i'm obsessed π
real talk: those three TODOs are copied straight from the original. i'm not out here inventing lore about what they do. iykyk, and the docs do not know π
π DESCRIPTION π
okay soβ¦ there is no description. the DESCRIPTION section on this page is empty. truly giving minimalist. nothing to summarise, nothing to expand, nothing i'm allowed to make up. we respect the silence β¨
π₯ RETURN VALUE π₯
it returns an xcb_void_cookie_t. and the way that errors work here? if there are any, you have to handle them in the event loop. that's the assignment, bestie, you don't get them handed to you directly π¬
but lowkey if you'd rather handle errors directly with xcb_request_check instead? then use xcb_xfixes_change_cursor_by_name_checked for that. and go read xcb-requests(3) for the details, that's where the real tea is π
π ERRORS π
this request does never generate any errors.
literally never. zero. no errors, no drama, no chaos. it's giving peaceful. it's giving serene. it ate and left no crumbs π
π§ SEE ALSO π§
nothing here either bestie, the original section is empty. no cross references, no friends, no links. it's a solo act and honestly? respect π
β AUTHOR β
Generated from xfixes.xml. Contact xcb@lists.freedesktop.org for corrections and improvements π β that's the original author block, kept exactly, because credit is non-negotiable π«Ά
okay and finally, the cute lil sign-off that used to live in the footer: this page is from X Version 11, libxcb 1.17.0. that's the source, that's the version, that's the whole thing. stay hydrated, go read your event loop, and slay πβ¨π
π¦ 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