TT_MESSAGE_OPNUM(3)

📦
version 2.5.3 · 2 versions
, in nixos 26.05

✨ NAME ✨

Okay bestie, welcome to the tt_message_opnum page from the library call manual 💖 This one is all about pulling the operation number attribute out of a message, and honestly? It’s giving “small function, big main-character energy” ✨

🦋 SYNOPSIS 🦋

#include &<Tt/tt_c.h>
int tt_message_opnum(
       Tt_message m);

🎀 DESCRIPTION 🎀

The tt_message_opnum function retrieves the operation number attribute from the specified message. Literally its whole job, and it ate 💅

The m argument is the opaque handle for the message involved in this operation. Opaque handle, bestie — don’t go poking at its insides, just pass it through 🫶

💖 RETURN VALUE 💖

Upon successful completion, the tt_message_opnum function returns the number of the operation involved in this message. The application can use tt_int_error(3) to extract one of the following Tt_status values from the returned integer:

  • 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 pointer energy 💀

🌈 SEE ALSO 🌈

Tt/tt_c.h — literally Tttt_c(5), tt_int_error(3). Yep, that’s the spelling in the page, bestie, I’m not touching it 💅

Cute lil sign-off: this is the tt_message_opnum page in the library call manual, and the footer/source tag is just that same library call identifier — no separate date or extra version line is listed in the source, so that’s the whole page, periodt 👑💖✨

📦 where this page comes from