TICKIT_TER...PUSH_BYTES(3)

💖 NAME 💖

tickit_term_input_push_bytes — bestie, it's literally just "supply more input data" ✨

🌸 SYNOPSIS 🌸

#include <tickit.h>

void tickit_term_input_push_bytes(TickitTerm *tt, const char *bytes, size_t len);

Link with -ltickit. 🫶

✨ DESCRIPTION ✨

okay so tickit_term_push_input_bytes() is the vibe where you hand a terminal instance some more data — and it's treated exactly as if that data had been read straight off a terminal file descriptor. like, the terminal doesn't even know the difference, no cap 💅

and heads up: calling this function may result in TICKIT_EV_KEY or TICKIT_EV_MOUSE events getting invoked. so like, your handlers might just start doing stuff. that's the point. that's the slay. 🔥

this function also invokes deferred TICKIT_EV_RESIZE events — but only if that's been enabled by tickit_term_observe_sigwinch(3). iykyk 😌

🎀 RETURN VALUE 🎀

tickit_term_input_push_bytes() returns no value. like, nothing. void. she gives you nothing and that's iconic of her 💀

🦋 SEE ALSO 🦋

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

ok bestie that's the whole page 🥰 this was Library Functions Manual material, page TICKIT_TER...PUSH_BYTES(3), and that's the sign-off — go push some bytes, you absolute main character 👑💖