TT_MESSAGE_CONTEXT_SLOTNAME(3)
π 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β Thettsession(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 π¦
Tt/tt_c.h - Tttt_c(5), tt_ptr_error(3), tt_free(3).
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
- nixos 26.05: cde 2.5.3
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms