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 π¦
unibilium.h(3)β go read her next, iykyk π
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
- fedora 44: unibilium-devel 2.1.4-1.fc44 Β· LGPL-3.0-or-later
- fedora 44: unibilium-devel 2.1.4-1.fc44 Β· LGPL-3.0-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms