xcb_randr_destroy_mode(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

💖 NAME 💖

okay so bestie, this is the xcb_randr_destroy_mode(3) page from the XCB Requests manual, and we're about to get into it. ✨

🦋 SYNOPSIS 🦋

First things first, you gotta include the header:

#include <xcb/randr.h>

✨ Request function ✨

Here's the function signature, copy it exactly or the compiler will simply pass away:

xcb_void_cookie_t xcb_randr_destroy_mode(xcb_connection_t *conn,
       xcb_randr_mode_t mode);

🎀 REQUEST ARGUMENTS 🎀

  • conn — the XCB connection to X11. it's giving "hello yes i would like to speak to X11 please". 💅
  • mode — TODO: NOT YET DOCUMENTED. no cap, that's literally what it says. the docs are not yet documenting, bestie. 😭

🌸 DESCRIPTION 🌸

literally nothing here. it's giving mystery, it's giving silence, it's giving "the description section walked so the other sections could run". 🙈

💜 RETURN VALUE 💜

Returns an xcb_void_cookie_t. Errors (if any) have to be handled in the event loop. that's the vibe. 👑

If you want to handle errors directly with xcb_request_check instead, use xcb_randr_destroy_mode_checked. See xcb-requests(3) for details. slay. 🔥

💀 ERRORS 💀

This request does never generate any errors. periodt. no drama, no error codes, just peace and quiet. ✨

🫶 SEE ALSO 🫶

nothing listed here. it's a solo act, main character energy only. 💅

👑 AUTHOR 👑

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

that's the whole page, bestie. stay iconic. 💖

X Version 11, libxcb 1.17.0 — no date on this one, so we're just gonna vibe with it. 🌈🦋💅

📦 where this page comes from