xcb_set_screen_saver(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_set_screen_saver πŸ’–

okay bestie, welcome to the xcb_set_screen_saver page β€” it's part of the XCB Requests crew (XCB = that X11 C binding we all know and love) πŸ¦‹

so like. you wanna tell the X server how to behave when your screen's been idle? that's literally this. let's go πŸ’…


✨ SYNOPSIS ✨

#include <xcb/xproto.h>

πŸŽ€ Request function πŸŽ€

xcb_void_cookie_t xcb_set_screen_saver(xcb_connection_t *conn,
       int16_t timeout, int16_t interval, uint8_t prefer_blanking,
       uint8_t allow_exposures);

that's the whole vibe right there. one function, four args, and a void cookie. slay ✨


🌸 REQUEST ARGUMENTS 🌸

  • conn β€” the XCB connection to X11. your lil link to the server, no cap 🫢
  • timeout β€” TODO: NOT YET DOCUMENTED. 😭 (yeah the docs really said "figure it out bestie")
  • interval β€” TODO: NOT YET DOCUMENTED. πŸ™ˆ (same energy, same mystery)
  • prefer_blanking β€” pick one of these cuties:
    • XCB_BLANKING_NOT_PREFERRED β€” TODO: NOT YET DOCUMENTED.
    • XCB_BLANKING_PREFERRED β€” TODO: NOT YET DOCUMENTED.
    • XCB_BLANKING_DEFAULT β€” TODO: NOT YET DOCUMENTED. and then, one more time for the people in the back: TODO: NOT YET DOCUMENTED. πŸ’€
  • allow_exposures β€” also a choose-your-own-adventure:
    • XCB_EXPOSURES_NOT_ALLOWED β€” TODO: NOT YET DOCUMENTED.
    • XCB_EXPOSURES_ALLOWED β€” TODO: NOT YET DOCUMENTED.
    • XCB_EXPOSURES_DEFAULT β€” TODO: NOT YET DOCUMENTED. and yes, once again: TODO: NOT YET DOCUMENTED. πŸ’€

πŸ’œ DESCRIPTION πŸ’œ

so bestie… the DESCRIPTION section on this page is empty. like, genuinely nothing. main character walked in, said absolutely nothing, and left. iconic behaviour honestly πŸ‘‘

(we're not gonna make stuff up for it either β€” no cap, we keep it exactly as empty as it is πŸ’–)


πŸ”₯ RETURN VALUE πŸ”₯

it hands you back an xcb_void_cookie_t. that's the whole return vibe.

and here's the thing: any errors (if there even are any) have to be handled in the event loop, so don't come crying to the return value about it 😌

now β€” if you'd rather deal with errors directly with xcb_request_check instead, then use xcb_set_screen_saver_checked and go off. xcb-requests(3) has the full tea on how that works πŸ“


🌈 ERRORS 🌈

this request does never generate any errors. never ever. zero. zilch. clean sheet. periodt ✨

🌟 SEE ALSO 🌟

nothing listed here, bestie β€” the SEE ALSO section is empty. an empty shelf. we respect it πŸŽ€


πŸ‘‘ AUTHOR πŸ‘‘

Generated from xproto.xml. Contact xcb@lists.freedesktop.org for corrections and improvements 🫢


and that's the page!! ok bye, go write some X11 code, you absolute legend πŸ’…πŸŒΈ

X Version 11 Β· libxcb 1.17.0 Β· this was xcb_set_screen_saver(3) β€” mwah, catch you in the next manpage, bestie πŸ’–βœ¨πŸ¦‹