unibi_name_num(3)

💖 unibi_name_num — the "what even is this capability called" era 💖

okay so bestie, we're deep in unibilium territory rn — this is the manual page for unibi_name_num(3) from the unibilium library, and it's literally just about turning capability enums into their names. that's the whole vibe. no cap. 🦋

---

✨ NAME ✨

unibi_name_bool, unibi_name_num, unibi_name_str, unibi_short_name_bool, unibit_short_name_num, unibi_short_name_str — translate capability enums to names 🎀

(yes, unibit_short_name_num is spelled exactly like that, i'm not touching it, that's the canon name fr fr 💅)

---

🌸 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 these functions? they hand you back the names of capabilities as strings. that's it. that's the job. 💖

by default you get the long names — the ones the docs call "variable names". like, the full government name of the capability.

but if you're feeling ✨economical✨, the unibi_short_name_* variants give you the shorter ones instead — the "capnames". little nickname energy. 🌈

---

🫶 EXAMPLE 🫶

here's the whole thing in action, look at her go:

#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?? has_status_line is the long name, hs is the short one, and they're both right there in one printf. iconic behaviour honestly. 👑

---

👀 SEE ALSO 👀

• unibilium.h(3)

---

and that's the whole page bestie, you ate it up 🍓

little sign-off moment: this page is from unibilium-2.1.4, dated 2026-09-07, and it lives in section 3 of the manual under the name unibi_name_num. mwah 💋