xcb_change_save_set(3)
π xcb_change_save_set β bestie, let's talk save sets π
okay so this is a page from the XCB Requests corner of the xcb_change_save_set(3) manual, and honestly? It's a little chaotic but we're gonna get through it together. π«Ά
β¨ NAME β¨
xcb_change_save_set β changes a client's save set. That's it, that's the whole vibe. π
πΈ SYNOPSIS πΈ
First things first, you gotta bring in the header, no cap:
#include <xcb/xproto.h>
π¦ Request function π¦
Here's the function signature, copy it exactly bestie, character for character:
xcb_void_cookie_t xcb_change_save_set(xcb_connection_t *conn,
uint8_t mode, xcb_window_t window);
π REQUEST ARGUMENTS π
connβ the XCB connection to X11. Your little lifeline to the server, periodt.modeβ one of these values, pick your fighter:XCB_SET_MODE_INSERTβ TODO: NOT YET DOCUMENTED. π (the docs really said "figure it out", and I respect the honesty ngl)XCB_SET_MODE_DELETEβ TODO: NOT YET DOCUMENTED. π (same energy, same mystery)- Insert to add the specified window to the save set, or Delete to delete it from the save set. That's the actual functional difference, lowkey.
windowβ the window to add or delete to/from your save set. The main character of this whole operation. π
π DESCRIPTION π
TODO: explain what the save set is for. (Yeah. The original manpage literally says that. Not me being lazy, that's canon. π)
What we do know: this function either adds or removes the specified window to the client's (your application's) save set. So it's giving "either/or", it's giving binary, it's giving insert-or-delete. That's the whole move. β¨
π RETURN VALUE π
It returns an xcb_void_cookie_t. Errors (if any) have to be handled in the event loop β so don't be out here ignoring your event loop, it's not a vibe. π«
If you want to handle errors directly with xcb_request_check instead, use xcb_change_save_set_checked. See xcb-requests(3) for details. iykyk. π§
π₯ ERRORS π₯
xcb_match_error_tβ you created the specified window. Bestie. This does not make sense, you can only add windows created by other clients to your save set. Not your window, not your save set. π ββοΈxcb_value_error_tβ you specified an invalid mode. The mode was not moding. πxcb_window_error_tβ the specified window does not exist. She's not real, she's gone, ghosted. π»
π SEE ALSO π
xcb-requests(3), xcb_reparent_window(3) β go read these too, they're iconic in their own right. π
π AUTHOR π
Generated from xproto.xml. Contact xcb@lists.freedesktop.org for corrections and improvements. They're literally asking for your feedback, so don't be shy. π
okay so real talk: this page has two big fat "TODO"s in it, and I'm not about to invent lore that isn't there. If the docs say TODO, I say TODO. Facts are facts, no cap. π―
and that's the whole page, bestie!! π go forth and manage your save set responsibly. this was X Version 11, libxcb 1.17.0, and the page is xcb_change_save_set(3) β mwah, slay, 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