xcb_convert_selection(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

xcb_convert_selection πŸ’…βœ¨

okay bestie, this is the xcb_convert_selection page from XCB Requests β€” yes the manual section 3 one, the library-call one, not a command you type in your shell 🫢. Buckle up, it's short but it's got lore (well, it's got TODOs, which is basically the same thing).


✨ NAME ✨

xcb_convert_selection β€” literally it's the request that asks somebody to hand over a selection... and that's all the NAME section says, because the description field is empty, and we respect that πŸŽ€


✨ SYNOPSIS ✨

first things first, you gotta pull in the header, no cap:

#include <xcb/xproto.h>

🌸 Request function 🌸

and here's the actual vibe, the function signature, copy it exactly bestie:

xcb_void_cookie_t xcb_convert_selection(xcb_connection_t *conn,
       xcb_window_t requestor, xcb_atom_t selection, xcb_atom_t target,
       xcb_atom_t property, xcb_timestamp_t time);

✨ REQUEST ARGUMENTS ✨

  • conn β€” the XCB connection to X11. your link to the mothership, your group chat with the server πŸ’œ
  • requestor β€” TODO: NOT YET DOCUMENTED. bestie the docs said "figure it out" 😭
  • selection β€” TODO: NOT YET DOCUMENTED. iconic of them honestly
  • target β€” TODO: NOT YET DOCUMENTED.
  • property β€” TODO: NOT YET DOCUMENTED.
  • time β€” TODO: NOT YET DOCUMENTED. the whole list is TODOs, we love a mysterious queen πŸ™ˆ
no for real, that's what the original says for every single one of these. i'm not gatekeeping anything from you, there is genuinely nothing there to gatekeep πŸ’€

✨ DESCRIPTION ✨

...yeah. the DESCRIPTION section is empty. nothing. a blank. the void. it's giving "we'll fill this in later" and later never came πŸ¦‹


✨ RETURN VALUE ✨

you get back an xcb_void_cookie_t. that's the whole bag πŸ“¦.

and listen, because this matters: errors (if any) have to be handled in the event loop. you don't just get them handed to you, you gotta go get them.

but if you'd rather deal with errors directly using xcb_request_check instead, then use xcb_convert_selection_checked β€” the checked twin, the responsible sibling πŸ‘‘.

peep xcb-requests(3) for the details, it's the whole explainer on how this cookie situation works.


✨ ERRORS ✨

good news bestie: this request does never generate any errors. slay. zero drama. no error handling arc for you, you're free 🌈


✨ SEE ALSO ✨

nothing here. the SEE ALSO section is empty. no cross-refs, no friends, just vibes ⭐


✨ AUTHOR ✨

generated from xproto.xml. if you spot something wrong and wanna send corrections or improvements, hmu at xcb@lists.freedesktop.org β€” they're the ones who actually know things 🫢


and that's the page fr fr πŸ’– this one came to you from X Version 11 and libxcb 1.17.0 β€” go forth, convert some selections, and remember: TODOs are temporary, but xcb-requests(3) is forever πŸŽ€βœ¨