xcb_grab_server(3)
π xcb_grab_server(3) π
okay bestie, welcome to the manual page for xcb_grab_server(3) from the XCB Requests collection. yes it's short. yes it's iconic. no i will not be elaborating because the original doesn't elaborate either and i refuse to make stuff up. π
β¨ NAME β¨
xcb_grab_server β and that's literally it, the original NAME line is just the function name followed by a dash with nothing after it. the mystery. the intrigue. the vibe. π¦
β¨ SYNOPSIS β¨
first things first, you gotta pull in the header:
#include <xcb/xproto.h>
πΈ Request function πΈ
xcb_void_cookie_t xcb_grab_server(xcb_connection_t *conn,
π okay so real talk β that's exactly where the source manpage's synopsis stops. it's cut off mid-signature in the original, and i'm not about to invent the rest for you, because inventing flags is a crime and i'm not going down for it. what you see is what you get, fr fr.
β¨ REQUEST ARGUMENTS β¨
connβ your XCB connection to X11. that's the whole list, bestie, one (1) argument and it's the connection. the way that this request has exactly one thing to hand itβ¦ minimalism. main character energy. π
β¨ DESCRIPTION β¨
β¦
okay so. the DESCRIPTION section in the original is empty. there is nothing there. zero. nada. a whole heading with no body, which honestly is its own kind of statement. i'm not gonna pad it out with made-up lore about what grabbing a server does β if the manpage doesn't say it, i don't say it. π«Ά (iykyk.)
β¨ RETURN VALUE β¨
it hands you back an xcb_void_cookie_t. and here's the tea: errors (if any) have to be handled in the event loop, okay? that's the assignment. π
if you'd rather handle errors directly with xcb_request_check instead, then use xcb_grab_server_checked β that's literally what it's for. and go read xcb-requests(3) for the full details, no cap. β¨
β¨ ERRORS β¨
π This request does never generate any errors.
slay. zero errors. the vibes are immaculate, the request is well-behaved, nothing is going wrong here. periodt. π₯
β¨ SEE ALSO β¨
β¦
bestie. the SEE ALSO section is empty. no cross-references, no friends, no links, nothing. it's giving solo era. π (the descriptions above did mention xcb_request_check, xcb_grab_server_checked and xcb-requests(3) though, so those are your honorary mentions. π)
β¨ AUTHOR β¨
Generated from xproto.xml. if you've got corrections or improvements, hit up xcb@lists.freedesktop.org β they're the ones who wanna hear it. π¬
and that's the whole page, bestie!! π this one's from X Version 11, libxcb 1.17.0, filed under xcb_grab_server(3). go forth, grab your server, handle your errors in the event loop, and stay iconic. ππ¦β¨π
π¦ 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