unibi_get_name(3)

πŸ’– unibi_get_name(3) β€” the unibilium girlies' guide to terminal names πŸ’–

ok so bestie, we're in section 3 of the unibilium manual, and today's topic is terminal names β€” the whole unibi_get_name / unibi_set_name situation. pull up a chair, grab a boba, let's go πŸ§‹βœ¨


✨ NAME ✨

unibi_get_name, unibi_set_name β€” access the name of a terminal object 🏷️

like, that's it. that's the whole job. one gets, one sets, both live in the name department.


🌸 SYNOPSIS 🌸

#include <unibilium.h>

const char *unibi_get_name(const unibi_term *ut);
void unibi_set_name(unibi_term *ut, const char *s);

so you gotta #include <unibilium.h> first, obviously, and then it's just these two little icons 🫢


πŸ¦‹ DESCRIPTION πŸ¦‹

okay so here's the tea β˜•

  • unibi_get_name gets the name from ut.
  • unibi_set_name sets the name to s.

that's the whole dynamic. getter gets, setter sets. they ate πŸ’…

⚠️ okay but PAY ATTENTION bestie, because this one is important: unibi_set_name simply stores the pointer it is given. it will not free s. it will not make a copy of the string. no dupe, no clone, no backup copy, nothing. it's literally just holding onto your pointer like "yeah this is mine now" 😭 so if s goes away, changes, or gets freed while ut still points at it, that's on you. no cap.

🌈 RETURN VALUE 🌈

unibi_get_name returns a pointer to the name of the terminal. and where does that name come from, you ask? two options, bestie:

  1. it comes from a terminfo entry β€” specifically the part after the last '|' in the name section πŸ‘‘
  2. or it was set by unibi_set_name

either way you get a pointer back. iconic behavior fr fr ✨


πŸŽ€ SEE ALSO πŸŽ€

go read those too, they're the sibling pages, the whole friend group 🫢


and that's the page!! this little legend comes to you from unibilium-2.1.4, dated 2026-09-07 β€” mwah, stay hydrated, read your manpages, and remember: store the pointer, not the vibe πŸ’œπŸŒ™

unibi_get_name(3) β€” periodt. πŸŽ€

πŸ“¦ where this page comes from