xcb_copy_gc(3)
π 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 ππ
π¦
π¦ 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