unibi_set_bool(3)

✨ NAME ✨

okay so welcome to the unibilium manual page for unibi_set_bool(3) — but lowkey it's a whole squad of functions: unibi_get_bool, unibi_set_bool, unibi_get_num, unibi_set_num, unibi_get_str, unibi_set_str. their entire job? accessing the capabilities of a terminal object 💅 like, getting and setting the vibes of a terminal, basically.

---

🌸 SYNOPSIS 🌸

bestie, here's the whole lineup, exactly as it is, no notes:

#include <unibilium.h>

int unibi_get_bool(const unibi_term *ut, enum unibi_boolean b);
void unibi_set_bool(unibi_term *ut, enum unibi_boolean b, int x);

int unibi_get_num(const unibi_term *ut, enum unibi_numeric n);
void unibi_set_num(unibi_term *ut, enum unibi_numeric n, int x);

const char *unibi_get_str(const unibi_term *ut, enum unibi_string s);
void unibi_set_str(unibi_term *ut, enum unibi_string s, const char *x);

like... look at them. six icons. three getters, three setters, one header, zero drama 💖

---

🦋 DESCRIPTION 🦋

so what are we actually doing here? get/set boolean, numeric, and string capabilities. that's the whole tea. that's the assignment. ☕

and because the terminal world has absent capabilities (yes, some things just don't exist, relatable), here's how the void gets represented:

• absent numeric capabilities are represented as -1 — not zero, not a sad empty space, literally -1. iconic honestly.
• absent string capabilities are represented as "NULL".

🫶 okay so this next part is IMPORTANT, no cap. unibi_set_str simply stores the pointer it is given. it will not free x, and it will not make a copy of the string. it just holds onto your pointer like it's keeping a secret. so if whatever x points at wanders off or gets freed, that's on you, bestie. mind your memory. 💀

---

👑 SEE ALSO 👑

• unibilium.h(3)

---

and that's the whole page, babe. this little masterpiece is from unibilium-2.1.4, dated 2026-09-07 — literally serving terminal capability knowledge since forever. go forth and set your booleans. mwah. 💖✨🎀