TTTK_OP_STRING(3)

🌸 NAME 🌸

tttk_op_string — this is the library call manual page, and it maps a ToolTalk op code to a string. Slay ✨

🦋 SYNOPSIS 🦋

#include &<Tt/tttk.h>
char *tttk_op_string(
Tttk_op opcode);

💅 DESCRIPTION 💅

Okay so tttk_op_string is the function, and it returns a string containing the op for opcode. That's literally the whole vibe: op code in, string out 💖

🎀 RETURN VALUE 🎀

When it succeeds, tttk_op_string returns a string that can be freed using tt_free(3); otherwise, it returns NULL. No cap — if it doesn't succeed, you get NULL, and there is no string to free 😭

🔥 APPLICATION USAGE 🔥

The distinctions in the Tttk_op enumerated type are for programmer convenience, and elements of Tttk_op do not necessarily map one-to-one with op strings, since ToolTalk allows ops to be overloaded. That's the key lore 🧚

For example, TTME_EDIT and TTME_COMPOSE are overloaded on the same op (Edit), and the messages only vary by the Tt_mode of the first argument. Iconic overloading behavior, honestly 👑

🌈 SEE ALSO 🌈

• Tt/tttk.h - Tttttk(5)
• tt_message_op(3)
• tt_free(3)

---

That's the tttk_op_string page from the library call manual — footer energy, bestie — signing off 🫶💖