xcb_xfixes_get_cursor_name(3)

πŸ“¦
version 1.17.0 Β· 4 versions
, in alpine 3.22, alpine 3.23, alpine 3.24, arch rolling, centos-stream 10, debian trixie, fedora 43, fedora 44, nixpkgs unstable, opensuse-leap 16.0, ubuntu questing, ubuntu resolute, ubuntu stonking

πŸŽ€ NAME πŸŽ€

xcb_xfixes_get_cursor_name β€” bestie, this is a request from the XCB XFixes extension, living its life in the xcb_xfixes_get_cursor_name(3) manual page (XCB Requests, iykyk). It's the little function you call when you wanna know what a cursor is called. πŸ’…


✨ SYNOPSIS ✨

First things first, you gotta pull in the header:

#include <xcb/xfixes.h>

🌸 Request function 🌸

xcb_xfixes_get_cursor_name_cookie_t
       xcb_xfixes_get_cursor_name(xcb_connection_t *conn,
       xcb_cursor_t cursor);

πŸ¦‹ Reply datastructure πŸ¦‹

typedef struct xcb_xfixes_get_cursor_name_reply_t {
    uint8_t    response_type;
    uint8_t    pad0;
    uint16_t   sequence;
    uint32_t   length;
    xcb_atom_t atom;
    uint16_t   nbytes;
    uint8_t    pad1[18];
} xcb_xfixes_get_cursor_name_reply_t;

πŸ’– Reply function πŸ’–

xcb_xfixes_get_cursor_name_reply_t
       *xcb_xfixes_get_cursor_name_reply(xcb_connection_t *conn,
       xcb_xfixes_get_cursor_name_cookie_t cookie,
       xcb_generic_error_t **e);

πŸŽ€ Reply accessors πŸŽ€

char *xcb_xfixes_get_cursor_name_name(const
              xcb_xfixes_get_cursor_name_request_t *reply);

int xcb_xfixes_get_cursor_name_name_length(const
              xcb_xfixes_get_cursor_name_reply_t *reply);

xcb_generic_iterator_t xcb_xfixes_get_cursor_name_name_end(const
              xcb_xfixes_get_cursor_name_reply_t *reply);

πŸ’œ REQUEST ARGUMENTS πŸ’œ

  • conn β€” the XCB connection to X11, aka your little hotline to the server. 🫢
  • cursor β€” TODO: NOT YET DOCUMENTED. yeah bestie, the docs literally said "not yet" and left. iconic of them. 😭

🌈 REPLY FIELDS 🌈

  • response_type β€” the type of this reply, in this case XCB_XFIXES_GET_CURSOR_NAME. This field is also present in the xcb_generic_reply_t and can be used to tell replies apart from each other. it's giving name tag at a party. πŸŽ€
  • 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, so don't come for me. ✨
  • atom β€” TODO: NOT YET DOCUMENTED. πŸ™ˆ
  • nbytes β€” TODO: NOT YET DOCUMENTED. πŸ’€

πŸ’… DESCRIPTION πŸ’…

...so this section is empty in the original, bestie. no description, no vibes, just a blank page serving absolutely nothing. we move. 🧚


⭐ RETURN VALUE ⭐

You get back an xcb_xfixes_get_cursor_name_cookie_t. lowkey the cookie is just the appetizer β€” errors have to be handled when you call the reply function xcb_xfixes_get_cursor_name_reply. πŸ“

If you'd rather handle errors in the event loop instead, use xcb_xfixes_get_cursor_name_unchecked. See xcb-requests(3) for details.


πŸ”₯ ERRORS πŸ”₯

This request does never generate any errors. periodt. no drama, no error codes, nothing. the cleanest request in the group chat. πŸ‘‘


🌸 SEE ALSO 🌸

(empty in the original β€” nobody linked anything, so there's nothing to pass along. no cap. πŸ’œ)


πŸ‘‘ AUTHOR πŸ‘‘

Generated from xfixes.xml. Contact xcb@lists.freedesktop.org for corrections and improvements.


and that's the whole page, bestie!! this was X Version 11, libxcb 1.17.0 β€” stay hydrated, keep your connections open, and slay the cursor name retrieval πŸ’–βœ¨πŸ¦‹