TT_MESSAGE_STATUS_STRING(3)

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

πŸ’– NAME πŸ’–

tt_message_status_string β€” retrieve the character string stored with the status attribute for a message πŸŽ€βœ¨

hey bestie, you're reading the tt_message_status_string page from the library call manual, and it's lowkey iconic because it's all about scooping out the status string attached to a message πŸ’….

✨ SYNOPSIS ✨

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

πŸ¦‹ DESCRIPTION πŸ¦‹

okay so tt_message_status_string retrieves the character string stored with the status attribute for the specified message β€” it's giving β€œtell me the status tea, but as a string” πŸ“.

The m argument is the opaque handle for the message involved in this operation. treat it like the main character backstage pass for the message πŸŽŸοΈπŸ‘‘.

🌸 RETURN VALUE 🌸

Upon successful completion, tt_message_status_string returns the status string stored in this message. 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. πŸ’€

πŸŽ€ APPLICATION USAGE πŸŽ€

The application should use tt_free(3) to free any data stored in the address returned by the ToolTalk API β€” yes bestie, clean up your mess, it's self-care 🧚✨.

🌈 SEE ALSO 🌈

the friend group:


and that's the cute sign-off from the tt_message_status_string page in the library call manual β€” that's the footer's source/version/date situation, no extra date tea in the original, so byeee bestie πŸŽ€πŸ’–βœ¨

πŸ“¦ where this page comes from