TICKIT_TERM_SET_INPUT_FD(3)

✨ TICKIT_TERM_SET_INPUT_FD ✨

okay so bestie, we're in the Library Functions Manual 💖 and this is the page for tickit_term_set_input_fd and tickit_term_get_input_fd, the duo that handles terminal input. one of them is lowkey problematic though, and we're gonna talk about it. 🫶

🌸 NAME 🌸

tickit_term_set_input_fd, tickit_term_get_input_fd — manage terminal input 🎀

🦋 SYNOPSIS 🦋

#include <tickit.h>

void tickit_term_set_input_fd(TickitTerm *tt, int fd);
int tickit_term_get_input_fd(TickitTerm *tt);

Link with -ltickit.

💅 DESCRIPTION 💅

so. tickit_term_set_input_fd() — and I need you to hear me when I say this — is discouraged and applications should not be using it. like, at all. it's giving deprecated behavior energy, no cap. 💀

the glow-up move instead? use the open and input_fd fields of the TickitTermBuilder struct that you hand over to tickit_term_build(3). that's the main character path. ✨

tickit_term_get_input_fd() is the chill one — it just hands you back the input file descriptor that's currently associated, or -1 if literally none has been set. that's it. that's the whole vibe check. 🌈

⭐ RETURN VALUE ⭐

tickit_term_get_input_fd() returns a file descriptor, or -1. periodt. 👑

🍓 SEE ALSO 🍓

• tickit_term_build(3)
• tickit_term_bind_event(3)
• tickit_term(7)
• tickit(7)

okay that's the whole page, you ate it fr fr 🧚💜 and just so we're keeping it 💯 — this whole thing lives under TICKIT_TERM_SET_INPUT_FD(3) in the Library Functions Manual. that's the sign-off, mwah, go read tickit_term_build(3) instead of using the discouraged one bestie 😭🌸