xcb_dpms_get_version(3)
π« xcb_dpms_get_version(3) β XCB Requests π«
okay bestie, welcome to the xcb_dpms_get_version page from the XCB Requests fam π«Ά this is where you ask the X server "hey girl, what DPMS version are you running?" and it tells you. no cap.
β¨ NAME β¨
xcb_dpms_get_version β (the original literally leaves this blank, so likeβ¦ the name is the vibe. it does the version-asking thing π
)
β¨ SYNOPSIS β¨
#include <xcb/dpms.h>
π Request function
xcb_dpms_get_version_cookie_t
xcb_dpms_get_version(xcb_connection_t *conn,
uint16_t client_major_version, uint16_t client_minor_version);
π Reply datastructure
typedef struct xcb_dpms_get_version_reply_t {
uint8_t response_type;
uint8_t pad0;
uint16_t sequence;
uint32_t length;
uint16_t server_major_version;
uint16_t server_minor_version;
} xcb_dpms_get_version_reply_t;
π Reply function
xcb_dpms_get_version_reply_t
*xcb_dpms_get_version_reply(xcb_connection_t *conn,
xcb_dpms_get_version_cookie_t cookie, xcb_generic_error_t **e);
πΈ REQUEST ARGUMENTS πΈ
connβ your XCB connection to X11, the whole reason we're here πclient_major_versionβTODO: NOT YET DOCUMENTED.(the manpage is literally leaving us on read, sorry bestie π)client_minor_versionβTODO: NOT YET DOCUMENTED.(same energy, fr fr)
π¦ REPLY FIELDS π¦
response_typeβ the type of this reply, and in this case it'sXCB_DPMS_GET_VERSION. this field also shows up in thexcb_generic_reply_t, so you can use it to tell your replies apart from each other πsequenceβ the sequence number of the last request processed by the X11 server.lengthβ the length of the reply, in words (and a word is 4 bytes, periodt).server_major_versionβTODO: NOT YET DOCUMENTED.πserver_minor_versionβTODO: NOT YET DOCUMENTED.π
π DESCRIPTION π
(yeahβ¦ the original section is just. empty. it's giving mystery. it's giving "figure it out yourself, babe" β¨ not me adding anything that isn't there, because we don't do that π )
β RETURN VALUE β
Returns an xcb_dpms_get_version_cookie_t. the way that errors have to be handled when you call the reply function xcb_dpms_get_version_reply β like, that's where they show up, no cap.
If you'd rather handle errors in the event loop instead, use xcb_dpms_get_version_unchecked. see xcb-requests(3) for the deets π«Ά
π ERRORS π
This request does never generate any errors. iconic, honestly. zero drama. π
π₯ SEE ALSO π₯
(okay so the original lists absolutely nothing here. nothing. nada. a whole empty section. i'm as shook as you are π)
π§ AUTHOR π§
Generated from dpms.xml. Contact xcb@lists.freedesktop.org for corrections and improvements π
and that's the whole page bestie!! this little gem shipped as part of X Version 11, libxcb 1.17.0, and it lives in the XCB Requests corner of the manual πΈ go ask that server what version it's on, you absolute main character ππβ¨
π¦ 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