unibi_short_name_bool(3)

✨ NAME ✨

okay bestie, gather round 💖 this page is about unibi_name_bool, unibi_name_num, unibi_name_str, unibi_short_name_bool, unibit_short_name_num, unibi_short_name_str — and what they do is translate capability enums to names. yes literally that. enums go in, cute little name strings come out 🎀

this is all part of the unibilium manual, section 3, and the page itself is unibi_short_name_bool(3) — just so you know where you are, iykyk 🦋

---

🌸 SYNOPSIS 🌸

#include <unibilium.h>

const char *unibi_name_bool(enum unibi_boolean b);
const char *unibi_name_num(enum unibi_numeric n);
const char *unibi_name_str(enum unibi_string s);

const char *unibi_short_name_bool(enum unibi_boolean b);
const char *unibi_short_name_num(enum unibi_numeric n);
const char *unibi_short_name_str(enum unibi_string s);

---

💅 DESCRIPTION 💅

so the way that these work is: they hand you back the names of capabilities as strings. that's the whole vibe. ✨

by default you get the long names — the "variable names", the full ones, the ones that spell everything out. no cap.

but the unibi_short_name_* variants? those are the glow-down versions, and i mean that lovingly 🫶 they use the shorter "capnames" instead. shorter, snappier, still iconic.

---

🎀 EXAMPLE 🎀

#include <stdio.h>
#include <unibilium.h>

int main(void) {
  printf("%s - %s\n", unibi_name_bool(unibi_has_status_line), unibi_short_name_bool(unibi_has_status_line));
  /* Output:
     has_status_line - hs
  */
}

see how has_status_line and hs are giving the same energy but one of them texted you back in three seconds and the other wrote a whole paragraph? 😭 that's the difference. that's it. that's the example.

---

👑 SEE ALSO 👑

• unibilium.h(3)

---

and that's the whole page, bestie — go forth and name your capabilities 💜

sign-off time: this was unibilium-2.1.4, dated 2026-09-07, and the manual page is unibi_short_name_bool(3). periodt. 💅⭐