TT_MESSAGE_REPLY(3)

✨ NAME ✨

tt_message_reply — reply to a message 💌 — straight from the tt_message_reply(library call) manual, bestie.

🌸 SYNOPSIS 🌸

#include &<Tt/tt_c.h>
Tt_status tt_message_reply(
Tt_message m);

🦋 DESCRIPTION 🦋

Okay so tt_message_reply has one very main-character job: it tells the ToolTalk service that your process has handled the message and filled in all return values. No cap. ✨

Then the ToolTalk service sends the message back to the sending process and fills in the state attribute with TT_HANDLED. Slay. 💅

The m argument is the opaque handle for the message involved in this operation. That’s the whole vibe there. 🫶

💖 RETURN VALUE 💖

Upon successful completion, tt_message_reply returns the status of the operation as one of these Tt_status values:

• TT_OK — The operation completed successfully. ✨
• TT_ERR_NOMP — The ttsession(1) process is not running and the ToolTalk service cannot restart it. 😭
• TT_ERR_NOTHANDLER — This application is not the handler for this message. 🙈
• TT_ERR_POINTER — The pointer passed does not point to an object of the correct type for this operation. 💀
• TT_ERR_PROCID — The specified process identifier is out of date or invalid. 🚩

🌈 SEE ALSO 🌈

• Tt/tt_c.h - Tttt_c(5).

---

okay bye bestie 🫶 the footer is literally just tt_message_reply(library call) again — no extra source, version, or date line hiding down here, so that’s the whole page. periodt. 💅✨