xcb_bell(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_bell πŸ’–

okay bestie, welcome to the xcb_bell(3) page, straight outta the XCB Requests manual. she's little. she's mysterious. she's giving iconic enigma. let's get into it πŸŽ€


✨ NAME ✨

xcb_bell -

and that's it. that's the whole name section. no description after the dash. the manpage literally left it blank, and honestly? we respect the silence. the mystery is the point. iykyk πŸ’…


✨ SYNOPSIS ✨

first things first, you gotta pull in the header:

#include <xcb/xproto.h>

🌸 Request function 🌸

xcb_void_cookie_t xcb_bell(xcb_connection_t *conn, int8_t percent);

that's the whole signature, no cap. two args, one return, let's go πŸ¦‹


✨ REQUEST ARGUMENTS ✨

  • conn β€” your XCB connection to X11. that's the whole thing. that's the vibe. it's how you talk to the server, bestie, she needs her connection πŸ’œ
  • percent β€” okay so the manpage says, verbatim-ish, TODO: NOT YET DOCUMENTED. i'm not even kidding. she's undocumented. she's a mystery girl. we don't know what she wants, we just pass her an int8_t and hope for the best 😭
not me being fr: the documentation genuinely does not say what percent does. i will not be inventing a meaning for it. that's the whole note. respect the blank. πŸ™ˆ

✨ DESCRIPTION ✨

okay so this is the part where the manpage would explain everything.

it's empty.

like, empty empty. there is no description text here at all. no paragraphs, no notes, nothing. the page just... moves on to RETURN VALUE like nothing happened. and you know what? main character energy. she said "read the code, bestie" and left πŸ‘‘


✨ RETURN VALUE ✨

she hands you back an xcb_void_cookie_t πŸ’–

now here's the important bit β€” errors (if any) have to be handled in the event loop. you don't get them handed to you right here on the spot, okay? you gotta go get them yourself. periodt.

but if you'd rather handle errors directly with xcb_request_check instead, then babe you want xcb_bell_checked. different function, different energy. go look at xcb-requests(3) for all the details on how that works 🫢


✨ ERRORS ✨

good news, angel: this request does never generate any errors. πŸ’€βœ¨

not one. zero. she is flawless, she is unbothered, she simply vibes. πŸ¦‹


✨ SEE ALSO ✨

nothing. literally nothing. the section exists and there is not a single reference under it. she's alone in here. solitary queen πŸ‘‘ (well β€” the page does point you at xcb-requests(3) up in RETURN VALUE, so there's that πŸŽ€)


✨ AUTHOR ✨

Generated from xproto.xml. so, machine-made, but make it fashion 🧚

if you spot something wrong and want to send corrections or improvements, hit up xcb@lists.freedesktop.org β€” they take feedback, fr fr πŸ’Œ


and that's the page, bestie!! she's from X Version 11, she ships with libxcb 1.17.0, and her whole self is filed under xcb_bell(3). short page, huge aura. slay, go beep something πŸŒˆπŸ””πŸ’–