unibi_name_str(3)

πŸŽ€ NAME πŸŽ€

okay so bestie, welcome to unibi_name_str(3), from the unibilium manual β€” this is the page about turning capability enums into names ✨

The whole girlies in question: unibi_name_bool, unibi_name_num, unibi_name_str, unibi_short_name_bool, unibit_short_name_num, unibi_short_name_str β€” they translate capability enums to names πŸ’…


🌸 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 like, these functions hand you back the names of capabilities, as strings, that's it, that's the whole job 🫢

By default you get the long names β€” a.k.a. the "variable names". Lowkey the verbose ones, the ones that spell it all out πŸ’–

But if you're feeling efficient, the unibi_short_name_* variants are right there and they use the shorter "capnames" instead. short queen energy πŸ‘‘


πŸ’– EXAMPLE πŸ’–

fr fr here's how you'd actually use it:

#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 the long name is all <yellow>has_status_line</yellow> and the short one is just <green>hs</green>? both valid, both slay, pick your vibe 🌈


πŸ¦‹ SEE ALSO πŸ¦‹


okay that's the whole page, no cap πŸ’œ this was unibi_name_str(3) from unibilium-2.1.4, dated 2026-09-07 β€” love that for us, mwah, go forth and name your capabilities πŸŒΈβœ¨πŸ’…

πŸ“¦ where this page comes from