TICKIT_TERM_SET_UTF8(3)

πŸ’– TICKIT_TERM_SET_UTF8 πŸ’–

okay bestie, welcome to tickit_term_set_utf8(3) β€” that's the page for the tickit_term_set_utf8 and tickit_term_get_utf8 girlies, hanging out in the Library Functions Manual. we're controlling UTF-8 mode today and honestly? it's giving main character energy. ✨


🌸 NAME 🌸

tickit_term_set_utf8, tickit_term_get_utf8 β€” control UTF-8 mode πŸ¦‹


✨ SYNOPSIS ✨

#include <tickit.h>

void tickit_term_set_utf8(TickitTerm *tt, bool utf8);
TickitMaybeBool tickit_term_get_utf8(TickitTerm *tt);

and don't forget, you gotta link with -ltickit πŸ’…


πŸŽ€ DESCRIPTION πŸŽ€

so, tickit_term_set_utf8() is the one that decides whether terminal input gets processed according to UTF-8 rules, or the legacy 8-bit single byte rules. literally two whole vibes, you pick one. πŸ™ˆ

and listen β€” if you don't call this function explicitly, it's not just gonna sit there clueless. it gets detected automatically by inspecting locale variables. no cap, it does it itself. iconic behaviour fr fr. πŸ‘‘

then we have tickit_term_get_utf8(), which hands you back the current value for UTF-8 support. it returns one of:

  • TICKIT_YES β€” yes bestie πŸ’–
  • TICKIT_NO β€” no bestie πŸ’€
  • TICKIT_MAYBE β€” the value is not yet known and hasn't been explicitly set 🫠

it's a whole tri-state situation and honestly that's so valid of it.


⭐ RETURN VALUE ⭐

  • tickit_term_set_utf8() returns no value. it's a void girlie, gives you nothing back, that's just her. πŸ’…
  • tickit_term_get_utf8() returns a TickitMaybeBool tri-state boolean value. yes/no/maybe, the full spectrum. 🌈

🌟 SEE ALSO 🌟


and that's the whole page bestie, no notes. that's the tea straight from the <strong>Library Functions Manual</strong> β€” page tickit_term_set_utf8(3), coming at you from the TICKIT_TERM_SET_UTF8(3) corner of the universe. mwah, take care of your terminal and she'll take care of you 🫢✨