TT_MESSAGE_CONTEXT_SLOTNAME(3)

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

πŸ’– NAME πŸ’–

tt_message_context_slotname β€” return the name of a message's nth context

okay bestie, welcome to the tt_message_context_slotname(library call) page πŸ’– this is the library-call manual for grabbing the name of a message's nth context, and yes, we're gonna keep every single detail intact.


✨ SYNOPSIS ✨

       #include &<Tt/tt_c.h>
       char *tt_message_context_slotname(
       Tt_message m,
       int n);

πŸŽ€ DESCRIPTION πŸŽ€

The tt_message_context_slotname function returns the name of a message's nth context. Slay.

The m argument is the opaque handle for the message involved in this operation 🫢. The n argument is the number of the context to be retrieved. The first context is numbered zero β€” zero-based indexing ate, no cap πŸ’….


πŸ’… RETURN VALUE πŸ’…

Upon successful completion, the tt_message_context_slotname function returns the contents for the message argument ✨. 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. iconic πŸŽ€
  • TT_ERR_NOMP β€” The ttsession(1) process is not running and the ToolTalk service cannot restart it 😭.
  • TT_ERR_NUM β€” The integer value passed was invalid (out of range).
  • TT_ERR_POINTER β€” The pointer passed does not point to an object of the correct type for this operation.

🌸 APPLICATION USAGE 🌸

The application can use tt_free(3) to free any data stored in the address returned by the ToolTalk API 🧚.


πŸ¦‹ SEE ALSO πŸ¦‹


xoxo, your footer bestie πŸŽ€ the footer literally signs off with tt_message...xt_slotname(library call) β€” that's the source/version/date line as printed, and we're obsessed with the consistency πŸ’–βœ¨

πŸ“¦ where this page comes from