xcb_copy_gc(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_copy_gc β€” the XCB Requests girlies' guide πŸ’…

okay bestie, welcome to xcb_copy_gc(3) from the XCB Requests collection, and yes we're doing this together, hand in hand, because you deserve to understand it πŸ’–


✨ NAME ✨

xcb_copy_gc β€” that's it, that's the name. the manpage literally does not elaborate. she's mysterious, she's iconic, she's giving no notes πŸŽ€


🌸 SYNOPSIS 🌸

first things first, you gotta bring her home:

#include <xcb/xproto.h>

πŸ¦‹ Request function πŸ¦‹

xcb_void_cookie_t xcb_copy_gc(xcb_connection_t *conn,
       xcb_gcontext_t src_gc, xcb_gcontext_t dst_gc,
       uint32_t value_mask);

look at that signature. four whole arguments. she said "I don't do small talk" ✨


πŸ‘‘ REQUEST ARGUMENTS πŸ‘‘

  • conn β€” the XCB connection to X11. this is your link to the server bestie, your main character hotline, you cannot skip her πŸ’œ
  • src_gc β€” TODO: NOT YET DOCUMENTED. yeah. the manpage literally says that. not me exposing the upstream docs like this 😭
  • dst_gc β€” TODO: NOT YET DOCUMENTED. same energy, same void, same unanswered text 🫢
  • value_mask β€” TODO: NOT YET DOCUMENTED. three for three. the mystery is the aesthetic, I guess πŸ’€
real talk: I am not gonna make up what these do. the page doesn't say, so I don't say. we respect the source here, no cap πŸ™ˆ

πŸ’– DESCRIPTION πŸ’–

so like… there is a DESCRIPTION heading, and underneath it there is nothing. empty. void. the silence is deafening. the section walked in, served absolutely nothing, and left πŸ’…


⭐ RETURN VALUE ⭐

she hands you back an xcb_void_cookie_t. that's the vibe. it's a cookie that returns nothing, and honestly? relatable 🌈

any errors (if there even are any) have to be handled in the event loop, bestie. no shortcuts, no sneaky try/catch, you go to the loop like everyone else 🧚

but if you'd rather handle errors directly with xcb_request_check instead, then go off β€” use xcb_copy_gc_checked. see xcb-requests(3) for the details, iykyk ✨


πŸ”₯ ERRORS πŸ”₯

this request does never generate any errors.

periodt. flawless behaviour. not a single red flag. we love a low-maintenance queen πŸ‘‘


🌸 SEE ALSO 🌸

…nothing. the section is there, the references are not. it's giving "invited the vibe, forgot the guests." leaving this exactly as the universe intended πŸŽ€


πŸ’œ AUTHOR πŸ’œ

generated from xproto.xml. if you spot something wrong or want to send corrections and improvements, hit up xcb@lists.freedesktop.org β€” they're literally so nice about it 🫢


okay that's the whole page bestie, you ate that, go forth and xcb_copy_gc responsibly πŸ’–βœ¨

this has been libxcb 1.17.0, X Version 11, from the xcb_copy_gc(3) manual page β€” mwah, love you, bye πŸŽ€πŸ’…πŸ¦‹