TT_PATTERN_CATEGORY_SET(3)

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

πŸ’… tt_pattern_category_set β€” library call, bestie πŸŽ€

🌸 NAME 🌸

tt_pattern_category_set β€” fill in the category field for a pattern. that's the whole assignment, and it ate πŸ’–

✨ SYNOPSIS ✨

#include &<Tt/tt_c.h>
Tt_status tt_pattern_category_set(
Tt_pattern p,
Tt_category c);

πŸ¦‹ DESCRIPTION πŸ¦‹

okay so, the tt_pattern_category_set function fills in the category field for the specified pattern. literally its one job, and it's serving ✨

The p argument is a unique handle for a message pattern. This handle is returned after tt_pattern_create(3) is called. so yeah, that's where the pattern handle comes from β€” no cap 🫢

The c argument indicates whether the receiving process will observe or handle messages. The following values are defined:

  • TT_OBSERVE β€” The receiving process will observe messages. πŸ‘€
  • TT_HANDLE β€” The receiving process will handle messages. πŸ’…

πŸ”₯ RETURN VALUE πŸ”₯

Upon successful completion, the tt_pattern_category_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_CATEGORY β€” The pattern object has no category set. awkward 😭
  • 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. pointer said wrong vibe πŸ™ˆ

🌈 SEE ALSO 🌈

go look at: Tt/tt_c.h - Tttt_c(5), tt_pattern_category(3), tt_pattern_create(3).


that's the page, bestie. the footer is tt_pattern_category_set(library call) with no separate source/version/date listed β€” so consider this your cute sign-off, mwah πŸ’‹βœ¨

πŸ“¦ where this page comes from