TT_MESSAGE_SENDER_PTYPE(3)

📦
version 2.5.3 · 2 versions
, in nixos 26.05

💅 tt_message_sender_ptype

okay so bestie, this is the library call manual page for tt_message_sender_ptype — and it's giving “retrieve the sender ptype attribute from a message” energy. iconic. 💖

✨ NAME ✨

tt_message_sender_ptype — retrieve the sender ptype attribute from a message. 🎀

🦋 SYNOPSIS 🦋

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

🌸 DESCRIPTION 🌸

tt_message_sender_ptype retrieves the sender ptype attribute from the specified message.

The m argument is the opaque handle for the message involved in this operation — like the message's little backstage pass 💅.

🎀 RETURN VALUE 🎀

Upon successful completion, tt_message_sender_ptype returns the sending process. 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. 🎉
  • TT_ERR_NOMP — The ttsession(1) process is not running and the ToolTalk service cannot restart it. 😭
  • TT_ERR_POINTER — The pointer passed does not point to an object of the correct type for this operation. 💀
bestie, the pointer is the main character here — use tt_ptr_error(3) to find out which Tt_status vibe you're getting ✨

🌈 APPLICATION USAGE 🌈

The application should use tt_free(3) to free any data stored in the address returned by the ToolTalk API. Don't leave that memory hanging, bestie — tt_free(3) is literally right there 🫶.

👑 SEE ALSO 👑

Sign-off: that's the tt_message_sender_ptype page from the library call manual 💖 the footer didn't list a separate source/version or date line, so I'm not making one up — periodt ✨

📦 where this page comes from