xcb_dpms_select_input(3)

📦
version 1.17.0 · 2 versions
  • 1.17.0 · 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 (latest)
  • 1.15 · ubuntu noble
, 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

💖 NAME 💖

xcb_dpms_select_input — okay so bestie, this page is lowkey the mystery girl of the manpage world. There is literally no description written here. The NAME section is giving blank canvas, main character with no backstory. But the function name itself? Iconic. We ride anyway. 🎀

This one lives in the xcb_dpms_select_input(3) manpage, manual section 3, and it's part of the XCB Requests crew.

✨ SYNOPSIS ✨

🌸 Request function

#include <xcb/dpms.h>
xcb_void_cookie_t xcb_dpms_select_input(xcb_connection_t *conn,
       uint32_t event_mask);
Note the return type bestie — it's an xcb_void_cookie_t, so this request does not hand you back any data directly. It's the "fire and forget (but politely)" vibe. 💅

🫶 REQUEST ARGUMENTS 🫶

  • conn — the XCB connection to X11. Your lil hotline to the X server, fr fr. 🌈
  • event_mask — TODO: NOT YET DOCUMENTED. Yeah. That's all the manpage says. Not me exposing the docs like this 😭. It's a uint32_t, that's what we know, that's what we're working with.

🦋 DESCRIPTION 🦋

So, the DESCRIPTION section here is... empty. Completely. Nothing. A whole void. The original manpage just has the heading and then vibes. 🙈

I am not about to invent lore for you, bestie — that would be lying and lying is not slay. So: the description is literally blank in the source. What we do know is in the sections above and below, periodt.

👑 RETURN VALUE 👑

Returns an xcb_void_cookie_t. That means if there are any errors, you have to go handle them in the event loop — the cookie doesn't scream at you directly. 🍓

If you'd rather handle errors directly with xcb_request_check instead, use xcb_dpms_select_input_checked. See xcb-requests(3) for the details. (That's a real reference, go read it, iykyk.) ⭐

💀 ERRORS 💀

Good news era: this request does never generate any errors. Not a single one. Zero. No cap. She's a clean girl, she's unproblematic, she's never gonna text you back with an error. 🧚

🌟 SEE ALSO 🌟

This section is empty in the original. No cross-references listed, no friends tagged, no mutuals. It's giving lone wolf. 💜

💖 AUTHOR 💖

Generated from dpms.xml. Contact xcb@lists.freedesktop.org for corrections and improvements. 📧

Okay that's the whole page, bestie! This came from the X Version 11 era, libxcb 1.17.0, and it's dated right there in the footer alongside the manual section. Go forth, select your inputs, handle your cookies in the event loop, and stay iconic. Mwah. 💅✨🎀🦋🌸🔥👑🌈⭐💀🙈🍓🧚💜🫶

📦 where this page comes from