TT_PATTERN_SCOPE_ADD(3)

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

✨ NAME ✨

tt_pattern_scope_add β€” add a value to the scope field for a pattern. Okay bestie, this is the tt_pattern_scope_add page from the library call manual πŸ’–

πŸ¦‹ SYNOPSIS πŸ¦‹

#include &<Tt/tt_c.h>
Tt_status tt_pattern_scope_add(
Tt_pattern p,
Tt_scope s);

πŸ’– DESCRIPTION πŸ’–

So tt_pattern_scope_add is the function that adds a value to the scope field for the pattern you're working with. Slay.

The p argument is a unique handle for a message pattern. You get this handle back after tt_pattern_create(3) is called. The s argument specifies what processes are eligible to receive the message. The following values are defined:

  • TT_SESSION β€” all processes joined to the indicated session are eligible. πŸ’…
  • TT_FILE β€” all processes joined to the indicated file are eligible. πŸŽ€
  • TT_BOTH β€” all processes joined to either indicated file or the indicated session are eligible. ✨
  • TT_FILE_IN_SESSION β€” all processes joined to both the indicated file and the indicated session are eligible. πŸ¦‹

πŸ‘‘ RETURN VALUE πŸ‘‘

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

  • TT_OK β€” the operation completed successfully. 🌈
  • 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 πŸŽ€

Peep these: Tt/tt_c.h - Tttt_c(5), tt_pattern_create(3).

byeee from the library call edition of tt_pattern_scope_add β€” source/version/date footer vibe included, bestie πŸ’œπŸ«Ά

πŸ“¦ where this page comes from