TT_MESSAGE_SESSION(3)

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

πŸ’– NAME πŸ’–

tt_message_session β€” retrieve the session attribute from a message. Also, hi bestie, this is a library call manual page, and it’s literally here to explain how to pull the session attribute out of a message. 🫢


✨ SYNOPSIS ✨

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

πŸ¦‹ DESCRIPTION πŸ¦‹

tt_message_session is the function that retrieves the session attribute from the specified message. No cap, that’s the whole vibe. πŸ’…

The m argument is the opaque handle for the message involved in this operation. Keep it cute, keep it opaque. πŸŽ€


🌸 RETURN VALUE 🌸

Upon successful completion, tt_message_session returns the identifier of the session to which this message applies. 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. 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. πŸ’€

πŸŽ€ APPLICATION USAGE πŸŽ€

The application should use tt_free(3) to free any data stored in the address returned by the ToolTalk API. Don’t forget, bestie β€” free the data, keep the vibes immaculate. ✨


⭐ SEE ALSO ⭐

Go peek at these, iykyk:


And that’s the whole page, bestie! πŸ’– Footer sign-off: this one ends with tt_message_session(library call) β€” that’s the source/version/date line, so we’re officially out. 🫢✨

πŸ“¦ where this page comes from