TTTK_MESSAGE_REJECT(3)

💖 tttk_message_reject — reject a message 💖

okay so bestie, welcome to the tttk_message_reject(library call) page — yes, it’s a library call, and yes, we’re gonna make it make sense 💅. This is the whole reject-a-message situation, with zero boring parts skipped ✨.

🌸 NAME 🌸

tttk_message_reject — reject a message

✨ SYNOPSIS ✨

#include &<Tt/tttk.h>
Tt_status tttk_message_reject(
Tt_message msg,
Tt_status status,
const char *status_string,
int destroy);

🎀 DESCRIPTION 🎀

okay so here’s the tea: tttk_message_reject sets the status and status string of the TT_REQUEST msg, rejects the msg, and then destroys msg if destroy is True. the way that it does all that in one call is giving main-character cleanup energy, fr fr ✨.

🔥 RETURN VALUE 🔥

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

• TT_OK — the operation completed successfully. slay ✨
• 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. not me being the wrong handler 💀
• TT_ERR_POINTER — the pointer passed does not point to an object of the correct type for this operation. pointer vibe check failed 🚨

🌈 SEE ALSO 🌈

Go peek at these, bestie — iykyk:

Tt/tttk.h - Tttttk(5), tt_message_reject(3), tttk_message_fail(3), tttk_message_abandon(3), tttk_message_fail(3).

---

That’s a wrap on the tttk_message_reject page, bestie — library-call edition all the way, and the footer didn’t print a date, so we’re keeping it cute and honest. Catch you in the next one 💖✨