xcb_randr_del...ider_property(3)
β¨ NAME β¨
xcb_randr_delete_provider_property β bestie, the description is literally empty in the source. It's giving "mystery", it's giving "figure it out yourself". No cap, the original just leaves that blank, so we're keeping it blank. π
π SYNOPSIS π
#include <xcb/randr.h>
π Request function
xcb_void_cookie_t
xcb_randr_delete_provider_property(xcb_connection_t *conn,
xcb_randr_provider_t provider, xcb_atom_t property);
πΈ REQUEST ARGUMENTS πΈ
connβ the XCB connection to X11, aka your hotline to the X server. She's the main character here, always. πproviderβ ok so the original saysTODO: NOT YET DOCUMENTED.and honestly? Same. That's all we've got. No extra lore, no invented facts, just vibes and a promise. π«Άpropertyβ alsoTODO: NOT YET DOCUMENTED.We are NOT making anything up about this one, bestie, that would be a lie and lying is not iconic. π
π¦ DESCRIPTION π¦
The DESCRIPTION section of the original is empty. Literally nothing. A void. A silence. A blank space (Taylor's version). We respect the mystery and we do not fill it in with guesses, because guessing at technical behaviour is the one thing that is not slay. β¨
π₯ RETURN VALUE π₯
She returns an xcb_void_cookie_t. That's it, that's the whole bag.
Any errors (if there are any, and there's a plot twist coming, keep reading) have to be handled over in the event loop. So you don't get them handed to you on a little platter, you go collect them yourself. π
But wait β if you'd rather handle errors directly, like right in your face, with xcb_request_check, then use xcb_randr_delete_provider_property_checked instead. That's your girl for the direct route. See xcb-requests(3) for all the deets. π
π ERRORS π
This request does never generate any errors. Periodt. Zero. None. A perfectly behaved little angel. π
π SEE ALSO π
The original leaves this section empty β no references, no cross-links, nothing. Just an empty shelf. We're not adding any because that would be making stuff up. π
β AUTHOR β
Generated from randr.xml. If you've got corrections or improvements, hit up xcb@lists.freedesktop.org. They're literally asking for your input, so don't be shy. π«Ά
Ok bye bestie, drink water, handle your errors in the event loop, and remember: X Version 11, libxcb 1.17.0, xcb_randr_del...ider_property(3). Mwah. π
β¨
π¦ 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