TT_MESSAGE_SENDER(3)

πŸ“¦
version 2.5.3 Β· 2 versions
, in nixos 26.05

✨ NAME ✨

tt_message_sender β€” from the library call manual: retrieve the sender attribute from a message. πŸ’Œ

🌸 SYNOPSIS 🌸

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

πŸ’… DESCRIPTION πŸ’…

Okay so tt_message_sender retrieves the sender attribute from the message you point it at. The m argument is the opaque handle for the message involved in this operation. 🫢

πŸ”₯ RETURN VALUE πŸ”₯

Upon successful completion, tt_message_sender returns the character value that uniquely identifies the sending process. Iconic. Your app can use tt_ptr_error(3) to extract one of these Tt_status values from the returned pointer:

  • 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_POINTER β€” the pointer passed does not point to an object of the correct type for this operation. rude, but ok πŸ’€

πŸŽ€ APPLICATION USAGE πŸŽ€

Your app should use tt_free(3) to free any data stored in the address returned by the ToolTalk API. seriously bestie, free it fr fr 🧚

🌈 SEE ALSO 🌈


ok bye bestie πŸ’– β€” that's the whole tt_message_sender page from the library call manual. No source version or date is listed on the page, so no extra deets to spill. πŸŽ€

πŸ“¦ where this page comes from