TT_MESSAGE_STATUS_SET(3)

✨ tt_message_status_set ✨

okay bestie, welcome to this library call page — the manual name is literally “library call,” and the function is tt_message_status_set. It’s giving “one job, done cute”: set the status attribute on a message. 💅

---

🌸 NAME 🌸

tt_message_status_set — set the status attribute for a message. periodt. 💖

🦋 SYNOPSIS 🦋

#include &<Tt/tt_c.h>
Tt_status tt_message_status_set(
Tt_message m,
int status);

Copy that exactly, character for character — including the & in the include line, bestie 😤✨

💅 DESCRIPTION 💅

So tt_message_status_set does exactly what it says on the tin: it sets the status attribute for the specified message. main character behavior, honestly.

The m argument is the opaque handle for the message involved in this operation — that’s your little ticket to the message you’re touching. The status argument is the status to be stored in this message. no cap. 🫶

🎀 RETURN VALUE 🎀

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

• 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 the bad-vibe case.
• TT_ERR_POINTER — The pointer passed does not point to an object of the correct type for this operation. 💀 pointer vibe check failed.

bestie, important: the status value must be greater than TT_ERR_LAST to avoid confusion with the ToolTalk service status values. That’s not a suggestion, okay? don’t skip it. 🚨

🔥 SEE ALSO 🔥

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

yes, Tttt_c(5) is exactly what the page says — iykyk, don’t come for me 💀

---

mwah 💋 — source/version: tt_message_status_set(library call); date: the footer’s date (not repeated here, bestie, because cute sign-off > copy-paste, fr fr) 🫶✨