TT_MESSAGE_HANDLER_PTYPE_SET(3)

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

πŸ’… tt_message_handler_ptype_set(3) πŸ’…

okay so this is the library call page for tt_message_handler_ptype_set, aka tt_message_...r_ptype_set(library call) energy in the header. We're setting a handler ptype attribute, and bestie, you're gonna get it. periodt. ✨


🌸 NAME 🌸

tt_message_handler_ptype_set β€” set the handler ptype attribute for a message 🫢

πŸŽ€ SYNOPSIS πŸŽ€

#include &<Tt/tt_c.h>
Tt_status tt_message_handler_ptype_set(
Tt_message m,
const char *ptid);

πŸ¦‹ DESCRIPTION πŸ¦‹

The tt_message_handler_ptype_set function sets the handler ptype attribute for the specified message. iconic behavior, no cap.

The m argument is the opaque handle for the message involved in this operation. The ptid argument is the type of process that is to handle this message. literally that's the whole vibe.

πŸ”₯ RETURN VALUE πŸ”₯

Upon successful completion, the tt_message_handler_ptype_set function returns the status of the operation as one of the following Tt_status values:

  • 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. πŸ’€

🌈 SEE ALSO 🌈

the cross-ref tea is right here: Tt/tt_c.h - Tttt_c(5). πŸ‘‘


okay that's the whole page, bestie 🫢 β€” source/version vibes: library call; date vibes: not printed in the footer, so we're not inventing one. no cap, that's the tea. πŸ’…

πŸ“¦ where this page comes from