TT_MESSAGE_ID(3)

💅 tt_message_id 💅

okay bestie, welcome to the tt_message_id page — it’s a library call manpage, and it’s literally about grabbing a message’s identifier. no cap. 🫶✨

✨ NAME ✨

tt_message_id — retrieve the identifier of a message 💌

🎀 SYNOPSIS 🎀

       #include &<Tt/tt_c.h>
       char *tt_message_id(
       Tt_message m);

🌸 DESCRIPTION 🌸

okay so the tt_message_id function retrieves the identifier of the specified message. that’s the whole assignment, and it ate. 💅

the m argument is the opaque handle for the message involved in this operation. yes, opaque — don’t peek behind the curtain, just pass the handle. 🫶

💖 RETURN VALUE 💖

upon successful completion, the tt_message_id function returns the character string value that uniquely identifies the message across all running ToolTalk sessions. iconic behavior. 👑

the identifier of the message is set at its creation and never changes. periodt. ⭐

the application can use tt_ptr_error(3) to extract one of the following Tt_status values from the returned pointer:

• TT_OK — the operation completed successfully. ✅ slay.
• TT_ERR_NOMP — the ttsession(1) process is not running and the ToolTalk service cannot restart it. 😭 that’s rough, bestie.
• TT_ERR_POINTER — the pointer passed does not point to an object of the correct type for this operation. 💀 wrong vibe, wrong pointer.

🦋 APPLICATION USAGE 🦋

the application should use tt_free(3) to free any data stored in the address returned by the ToolTalk API. yes bestie, free it — don’t just leave it there looking cute. 🎀

🔥 SEE ALSO 🔥

Tt/tt_c.h - Tttt_c(5), tt_ptr_error(3), tt_free(3).

---

cute sign-off: source/version vibes are tt_message_id in the library call section, and the original page didn’t list a date — so no date tea to spill, sorry bestie 💅✨