MAIL(4)

💌 NAME 💌

okay so like, this is Mail(special file) — the manual page for the Mail request, and it's literally the "compose or mail a document" girly 💅. yeah. that's her whole thing. she routes your doc to a destination through the mail message handling system, and the handler is the one doing the legwork of finding routing info inside the document. main character energy fr fr.

---

✨ SYNOPSIS ✨

[file] Mail(in mediaType contents);
[file] Mail([out|inout] mediaType contents
        [in title docName]);

two whole forms, bestie. pick your fighter 🫶

---

🌸 DESCRIPTION 🌸

so the Mail request tells the handler to route a document to a destination using the mail message handling system. and like — the handler is responsible for finding the routing information in the document. no cap, that's on them, not on you 💖

when the contents argument is of mode in, the handler must deliver the document as is, without interacting with the user. zero chat, zero vibes, just deliver 😌

when the contents argument is of mode inout or out, the handler must let the user compose or edit the document (and any embedded routing information) before it's delivered. oh and — if the handling tool supports some form of intermediate "save" operation, it must send a Deposit request back to the tool that initiated the Mail request. yes that's a whole thing, don't skip it 🎀

the contents argument is the contents of the document. if this argument is unset (in other words, has a value of (char *)0), then the contents of the document are in the file named in the message's file attribute. and the data type (mediaType) of the contents argument should be string, unless nulls are valid in the given media type, in which case the data type must be bytes. read that twice, it matters 🦋

the docName argument contains the name of the document. if the docName argument is absent and the file attribute is set, the file name is considered to be the title of the document. and like — this string would be suitable for display in a window title bar, for example. cute, right? 💖

---

🧚 APPLICATION USAGE 🧚

• the ttmedia_ptype_declare(3) function can be used to register for, and help process, this message ✨
• this message can be sent with the ttmedia_load(3) function 💫

---

💀 ERRORS 💀

the ToolTalk service may return one of the following errors while processing the Mail request (and yes, she might just do that, so brace yourself 🙈):

• TT_DESKTOP_ENOENT — the file that was alleged to contain the document does not exist. alleged!! 😭 that file is a no-show.
• TT_DESKTOP_ENODATA — the in-mode contents argument had no value and the file attribute of the message was not set. literally nothing to go on bestie 💀
• TT_MEDIA_ERR_FORMAT — the document is not a valid instance of the media type. wrong vibe, rejected 🚫

---

👑 SEE ALSO 👑

ttmedia_ptype_declare(3), ttmedia_load(3); Intro, Edit requests.

---

okay that's the whole page, go be iconic with it 🌈💜

sign-off time: this was Mail(special file) (yeah, she titled her own page twice, icon behaviour 👑), from the version/source line at the bottom of the original — dated and stamped as Mail(special file) in the footer. slay, mwah 💋🎀🦋