unibi_set_ext_bool_name(3)

✨ unibi_set_ext_bool_name(3) β€” the unibilium manual ✨

okay bestie, gather round, because we're talking about the names of extended capabilities on a terminal object and honestly? it's giving niche-but-essential πŸ’…


🌸 NAME 🌸

unibi_get_ext_bool_name, unibi_set_ext_bool_name, unibi_get_ext_num_name, unibi_set_ext_num_name, unibi_get_ext_str_name, unibi_set_ext_str_name β€” access the names of extended capabilities of a terminal object 🫢


πŸŽ€ SYNOPSIS πŸŽ€

#include <unibilium.h>

const char *unibi_get_ext_bool_name(const unibi_term *ut, size_t i);
const char *unibi_get_ext_num_name(const unibi_term *ut, size_t i);
const char *unibi_get_ext_str_name(const unibi_term *ut, size_t i);

void unibi_set_ext_bool_name(unibi_term *ut, size_t i, const char *s);
void unibi_set_ext_num_name(unibi_term *ut, size_t i, const char *s);
void unibi_set_ext_str_name(unibi_term *ut, size_t i, const char *s);

like yes, six functions, three getters and three setters, all sitting pretty in <unibilium.h> ✨


πŸ’– DESCRIPTION πŸ’–

so the whole vibe here is get/set the names of extended boolean, numeric, and string capabilities. that's it, that's the job. πŸ”₯

i is the index of the extended capability you're acting on. and ngl, it has rules: it must be less than unibi_count_ext_bool(ut), unibi_count_ext_num(ut), or unibi_count_ext_str(ut), respectively. pick the right count for the right flavour of capability, bestie, don't mix them up πŸ’€

⚠️ and now the part you need to hear: "unibi_set_ext_bool_name", "unibi_set_ext_num_name", and "unibi_set_ext_str_name" simply store the pointer they are given. they will not free s or make a copy of the string. no dupe, no cleanup, just vibes and a pointer. keep that string alive yourself, okay? 😭

πŸ¦‹ SEE ALSO πŸ¦‹


and that's the whole page, periodt πŸ‘‘ this one came from unibilium-2.1.4, dated 2026-09-07 β€” mwah, iconic, no cap πŸ’…πŸŒΈπŸ’œ

πŸ“¦ where this page comes from