xcb_randr_get_output_info(3)
π xcb_randr_get_output_info π
okay so bestie, welcome to the xcb_randr_get_output_info page from the XCB Requests manual β¨ this one lives in section 3 of the manual, and it's your little backstage pass to asking the X server everything about an output π«Ά
πΈ NAME πΈ
xcb_randr_get_output_info β bestie the description is literally blank in the source, no cap π (yes really, they left it empty, iconic of them)
β¨ SYNOPSIS β¨
#include <xcb/randr.h>
π Request function π
xcb_randr_get_output_info_cookie_t
xcb_randr_get_output_info(xcb_connection_t *conn,
xcb_randr_output_t output, xcb_timestamp_t config_timestamp);
π¦ Reply datastructure π¦
typedef struct xcb_randr_get_output_info_reply_t {
uint8_t response_type;
uint8_t status;
uint16_t sequence;
uint32_t length;
xcb_timestamp_t timestamp;
xcb_randr_crtc_t crtc;
uint32_t mm_width;
uint32_t mm_height;
uint8_t connection;
uint8_t subpixel_order;
uint16_t num_crtcs;
uint16_t num_modes;
uint16_t num_preferred;
uint16_t num_clones;
uint16_t name_len;
} xcb_randr_get_output_info_reply_t;
π Reply function π
xcb_randr_get_output_info_reply_t
*xcb_randr_get_output_info_reply(xcb_connection_t *conn,
xcb_randr_get_output_info_cookie_t cookie,
xcb_generic_error_t **e);
π Reply accessors π
xcb_randr_crtc_t *xcb_randr_get_output_info_crtcs(const
xcb_randr_get_output_info_request_t *reply);
int xcb_randr_get_output_info_crtcs_length(const
xcb_randr_get_output_info_reply_t *reply);
xcb_generic_iterator_t xcb_randr_get_output_info_crtcs_end(const
xcb_randr_get_output_info_reply_t *reply);
xcb_randr_mode_t *xcb_randr_get_output_info_modes(const
xcb_randr_get_output_info_request_t *reply);
int xcb_randr_get_output_info_modes_length(const
xcb_randr_get_output_info_reply_t *reply);
xcb_generic_iterator_t xcb_randr_get_output_info_modes_end(const
xcb_randr_get_output_info_reply_t *reply);
xcb_randr_output_t *xcb_randr_get_output_info_clones(const
xcb_randr_get_output_info_request_t *reply);
int xcb_randr_get_output_info_clones_length(const
xcb_randr_get_output_info_reply_t *reply);
xcb_generic_iterator_t xcb_randr_get_output_info_clones_end(const
xcb_randr_get_output_info_reply_t *reply);
uint8_t *xcb_randr_get_output_info_name(const
xcb_randr_get_output_info_request_t *reply);
int xcb_randr_get_output_info_name_length(const
xcb_randr_get_output_info_reply_t *reply);
xcb_generic_iterator_t xcb_randr_get_output_info_name_end(const
xcb_randr_get_output_info_reply_t *reply);
π REQUEST ARGUMENTS π
connβ your XCB connection to X11, the lil phone line to the server πoutputβ TODO: NOT YET DOCUMENTED. π the docs said "we'll get to it" and then never did, we've all been thereconfig_timestampβ TODO: NOT YET DOCUMENTED. π same energy, same empty plate
π REPLY FIELDS π
response_typeβ the type of this reply, in this caseXCB_RANDR_GET_OUTPUT_INFO. This field is also present in thexcb_generic_reply_tand can be used to tell replies apart from each other π it's the little name tag at the partysequenceβ the sequence number of the last request processed by the X11 server π’lengthβ the length of the reply, in words (a word is 4 bytes) πstatusβ TODO: NOT YET DOCUMENTED. πtimestampβ TODO: NOT YET DOCUMENTED. πcrtcβ TODO: NOT YET DOCUMENTED. πmm_widthβ TODO: NOT YET DOCUMENTED. πmm_heightβ TODO: NOT YET DOCUMENTED. πconnectionβ TODO: NOT YET DOCUMENTED. πsubpixel_orderβ TODO: NOT YET DOCUMENTED. πnum_crtcsβ TODO: NOT YET DOCUMENTED. πnum_modesβ TODO: NOT YET DOCUMENTED. πnum_preferredβ TODO: NOT YET DOCUMENTED. πnum_clonesβ TODO: NOT YET DOCUMENTED. πname_lenβ TODO: NOT YET DOCUMENTED. π
fr fr, every single one of these says "TODO: NOT YET DOCUMENTED." and I'm just the messenger π§ keeping it 100, bestie
π« DESCRIPTION π«
this section is literally empty in the original β¨ nothing, nada, a whole vibe of silence πΈ so we're keeping it exactly that way β no invented lore, no fake tea π«Ά
π₯ RETURN VALUE π₯
Returns an xcb_randr_get_output_info_cookie_t πͺ (yes, a cookie β you grab it now and cash it in later, main character energy).
Errors have to be handled when calling the reply function xcb_randr_get_output_info_reply.
If you'd rather handle errors in the event loop instead, use xcb_randr_get_output_info_unchecked. See xcb-requests(3) for details π
π ERRORS π
This request does never generate any errors. periodt. zero drama, zero chaos, she simply does not miss β¨
π SEE ALSO π
this section is empty in the original too, so there's nothing to link you to, bestie π iykyk
π AUTHOR π
Generated from randr.xml. Contact xcb@lists.freedesktop.org for corrections and improvements π (they're literally asking, so if you spot something, say something!)
and that's the whole page, bestie π this one shipped as X Version 11, libxcb 1.17.0 β mwah, iconic, no notes πβ¨π
π¦ 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