TTTK_MESSAGE_ABANDON(3)

📦
version 2.5.3 · 2 versions
, in nixos 26.05

💖 tttk_message_abandon — library call 💖

okay so bestie, welcome to the tttk_message_abandon page from the library call manual. Buckle up, we're finalizing messages with main character energy. 🎀

✨ NAME ✨

tttk_message_abandon — finalize a message properly. That's it, that's the name, and yes she's about to clean up a message she does not understand. 💅

🌸 SYNOPSIS 🌸

#include &<Tt/tttk.h>
Tt_status tttk_message_abandon(
Tt_message msg);

🦋 DESCRIPTION 🦋

so here's the situation, bestie: an app gets a message it does not understand, and it just wants to get rid of it. That's exactly when tttk_message_abandon comes in. It fails or rejects msg if appropriate, and then it destroys it. Poof. Gone. 💨

But plot twist: tttk_message_abandon will reject or fail the message only if msg is a TT_REQUEST in Tt_state TT_SENT. If it has a Tt_address of TT_HANDLER or a tt_message_status of TT_WRN_START_MESSAGE, then it fails the message; otherwise, it rejects it. In either case, tttk_message_abandon gives msg a message status (see tt_message_status(3)) of TT_DESKTOP_ENOTSUP. No cap. 🫶

🔥 RETURN VALUE 🔥

Upon successful completion, the tttk_message_abandon function returns the status of the operation as one of the following 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. 😭
  • TT_ERR_NOTHANDLER — This application is not the handler for this message. rude, but okay. 💀
  • TT_ERR_POINTER — The pointer passed does not point to an object of the correct type for this operation. check ur pointer bestie. 🙈

🌈 SEE ALSO 🌈

and that's the whole page, bestie — the footer/source-version-date situation is literally just tttk_message_abandon(library call), with no extra source/version/date line hiding in the original, so consider this your cute sign-off. 💖🎀✨

📦 where this page comes from