xcb_get_font_path(3)

💖 xcb_get_font_path — bestie's guide to the XCB request, from the xcb_get_font_path(3) manual 💖

okay so. we're in the XCB Requests corner of the universe, and today's main character is xcb_get_font_path. she's a request function. she asks the X server for the font path. that's the whole vibe. let's go 🦋

---

✨ NAME ✨

xcb_get_font_path — (yeah bestie the original literally leaves this blank, so we're keeping it blank, no cap 💀)

---

✨ SYNOPSIS ✨

#include <xcb/xproto.h>

🎀 Request function

xcb_get_font_path_cookie_t xcb_get_font_path(xcb_connection_t *conn,

🎀 Reply datastructure

typedef struct xcb_get_font_path_reply_t {
    uint8_t  response_type;
    uint8_t  pad0;
    uint16_t sequence;
    uint32_t length;
    uint16_t path_len;
    uint8_t  pad1[22];
} xcb_get_font_path_reply_t;

🎀 Reply function

xcb_get_font_path_reply_t
       *xcb_get_font_path_reply(xcb_connection_t *conn,
       xcb_get_font_path_cookie_t cookie, xcb_generic_error_t **e);

🎀 Reply accessors

int xcb_get_font_path_path_length(const xcb_get_font_path_reply_t
       *reply);

xcb_str_iterator_t xcb_get_font_path_path_iterator(const
       xcb_get_font_path_reply_t *reply);

like. look at those accessors. xcb_get_font_path_path_length gives you the length, xcb_get_font_path_path_iterator gives you an iterator. they're a lil duo, they slay together 👑

---

🌸 REQUEST ARGUMENTS 🌸

• conn — the XCB connection to X11. she's your line to the server, your little hotline. everything goes through her 💅

---

🌈 REPLY FIELDS 🌈

• response_type — the type of this reply, and in this case it's XCB_GET_FONT_PATH. this field also lives in the xcb_generic_reply_t, and it's literally how you tell one reply apart from another. it's giving name tag at a party 🏷️
• sequence — the sequence number of the last request the X11 server processed. tracking numbers but make it protocol ✨
• length — the length of the reply, measured in words. and bestie, a word is 4 bytes. do not forget that, i'm begging 😭
• path_len — TODO: NOT YET DOCUMENTED. like ok she's mysterious, she's giving ✨enigma✨, the docs simply did not show up 🙈

---

💜 DESCRIPTION 💜

okay so the DESCRIPTION section in the original is literally empty. nothing. a whole mood. we respect her silence 🫶

---

⭐ RETURN VALUE ⭐

she returns an xcb_get_font_path_cookie_t. yes, a cookie 🍪 (not the eating kind, sadly).

errors? you have to handle those when you call the reply function xcb_get_font_path_reply. that's the deal.

and if you'd rather handle errors in the event loop instead? use xcb_get_font_path_unchecked. and check xcb-requests(3) for the deets, because that page has the whole story 📖

---

💀 ERRORS 💀

this request does never generate any errors. ever. not one. she's the low-drama friend, she simply doesn't do chaos. periodt. 🙅♀️

---

🦋 SEE ALSO 🦋

the original SEE ALSO section is empty, bestie. nobody linked anybody. it's a lonely lil section and we're leaving it exactly as lonely as we found it 💔

---

👑 AUTHOR 👑

Generated from xproto.xml. if you've got corrections or improvements, hit up xcb@lists.freedesktop.org — they want your notes, fr fr 📬

---

and that's the whole page, bestie. run with it. 🌈✨

this has been your girl, signing off from X Version 11, libxcb 1.17.0, and the xcb_get_font_path(3) manual page. drink water, close your file descriptors, and slay 💅💖🎀