xcb_grab_server(3)

πŸ“¦
version 1.17.0 Β· 4 versions
, in alpine 3.22, alpine 3.23, alpine 3.24, arch rolling, centos-stream 10, debian trixie, fedora 43, fedora 44, nixpkgs unstable, opensuse-leap 16.0, ubuntu questing, ubuntu resolute, ubuntu stonking

πŸ’– 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. πŸŽ€πŸ¦‹βœ¨πŸ‘‘