xcb_randr_delete_output_mode(3)
π xcb_randr_delete_output_mode β bestie's guide to yeeting a mode off an output π
ok so like. this is a page from the XCB Requests corner of the manual, and it's about xcb_randr_delete_output_mode from <xcb/randr.h>. that's the header it lives in, btw. π
β¨ NAME β¨
xcb_randr_delete_output_mode β
ngl bestie the original manpage left this one blank. no description. nothing. iconic of them honestly. the name is the name and we move. π
πΈ SYNOPSIS πΈ
#include <xcb/randr.h>
π¦ Request function π¦
xcb_void_cookie_t xcb_randr_delete_output_mode(xcb_connection_t *conn,
xcb_randr_output_t output, xcb_randr_mode_t mode);
π REQUEST ARGUMENTS π
connβ the XCB connection to X11. like, your whole lil link to the X server. she's the main character here. πoutputβ TODO: NOT YET DOCUMENTED. yeah. the docs just. aren't there. not me reading the source for funsies πmodeβ TODO: NOT YET DOCUMENTED. same vibe, same energy. the original said nothing so i'm saying nothing. periodt. π
π DESCRIPTION π
so the DESCRIPTION section of the original is... empty. like genuinely zero words. a whole section with nothing in it. lowkey relatable, highkey unhelpful. i can't make up behaviour that isn't there, so i'm not gonna. we just vibe with the void. π«Ά
β RETURN VALUE β
it hands you back an xcb_void_cookie_t. that's the whole return situation.
any errors (if there even are any) have to be handled over in the event loop, bestie. that's just how void cookies work.
but wait β if you'd rather handle errors directly with xcb_request_check instead, then you want the checked twin:
xcb_randr_delete_output_mode_checked
see xcb-requests(3) for the deets on all that. π§
π₯ ERRORS π₯
this request does never generate any errors. not a single one. zero. she's chill like that. no cap. β¨
π SEE ALSO π
(empty. nothing here. the original really said "no links, no friends, only vibes" and honestly? respect. π)
π AUTHOR π
generated from randr.xml. if you got corrections or improvements, hit up xcb@lists.freedesktop.org. that's the whole author situation β it's a generated page, not a person, so be nice to the mailing list bestie. π
ok that's the page!! short, sweet, and fully documented (well, as documented as the original was, which is a choice π). this was X Version 11, libxcb 1.17.0, and you were reading xcb_randr_delete_output_mode(3). mwah, love u, go handle your cookies in the event loop πΈπβ¨
π¦ where this page comes from
- alpine 3.22: libxcb-doc 1.17.0-r0 Β· MIT
- alpine 3.23: libxcb-doc 1.17.0-r1 Β· MIT
- alpine 3.24: libxcb-doc 1.17.0-r2 Β· MIT
- arch rolling: libxcb 1.17.0-1 Β· X11
- centos-stream 10: libxcb-devel 1.17.0-3.el10 Β· X11
- debian trixie: libxcb-doc 1.17.0-2
- fedora 43: libxcb-devel 1.17.0-6.fc43 Β· X11
- fedora 43: libxcb-devel 1.17.0-6.fc43 Β· X11
- fedora 44: libxcb-devel 1.17.0-7.fc44 Β· X11
- fedora 44: libxcb-devel 1.17.0-7.fc44 Β· X11
- nixpkgs unstable: libxcb 1.17.0
- opensuse-leap 16.0: libxcb-devel-doc 1.17.0-160000.2.2 Β· MIT
- ubuntu questing: libxcb-doc 1.17.0-2build1
- ubuntu resolute: libxcb-doc 1.17.0-2ubuntu1
- ubuntu stonking: libxcb-doc 1.17.0-2ubuntu1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms