TT_MESSAGE_DISPOSITION(3)

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

πŸ’– tt_message_disposition (library call) πŸ’–

hey bestie 🫢 welcome to the page for tt_message_disposition(library call) β€” yes, it's a library call, and yes, we're retrieving the disposition attribute from a message. lowkey iconic. πŸ’…

✨ NAME ✨

tt_message_disposition β€” retrieve the disposition attribute from a message. that's the whole vibe, no cap.

🌸 SYNOPSIS 🌸

copy this exactly, bestie β€” i'm not touching the punctuation ✨

#include &<Tt/tt_c.h>
Tt_disposition tt_message_disposition(
Tt_message m);

πŸ’– DESCRIPTION πŸ’–

okay so the tt_message_disposition function retrieves the disposition attribute from the specified message. it's literally right there in the name.

The m argument is the opaque handle for the message involved in this operation. opaque handle means no peeking behind the curtain, bestie 🫢

πŸŽ€ RETURN VALUE πŸŽ€

Upon successful completion, the tt_message_disposition function returns a value that indicates whether an instance of the receiving process should be started to receive the message immediately, or whether the message is to be queued until the receiving process is started at a later time. okay so it's a start-now-or-wait-later vibe check. The tt_message_disposition function returns one of the following Tt_disposition values:

  • TT_DISCARD β€” There is no receiver for this message. The message will be returned to the sender with the Tt_status field containing TT_FAILED. no receiver, no cap.
  • TT_QUEUE β€” Queue the message until a process of the proper ptype receives the message. wait for it...
  • TT_START β€” Attempt to start a process of the proper ptype if none is running. start it up, bestie.
  • TT_QUEUE+TT_START β€” Queue the message and attempt to start a process of the proper ptype if none is running. both? both. iconic.

The application can use tt_int_error(3) to extract one of the following Tt_status values from the Tt_disposition integer: iykyk.

  • TT_OK β€” The operation completed successfully. slay.
  • TT_ERR_NOMP β€” The ttsession(1) process is not running and the ToolTalk service cannot restart it. big yikes.
  • TT_ERR_POINTER β€” The pointer passed does not point to an object of the correct type for this operation. wrong vibe, wrong type.

πŸ¦‹ SEE ALSO πŸ¦‹

the receipts:


mwah πŸ’‹ β€” signing off from the tt_message_disposition(library call) page. source/version/date: not listed in the original footer, bestie β€” so i'm not making one up. 🫢✨

πŸ“¦ where this page comes from