PRINT(4)

🖨️ Print — print a document

okay bestie, welcome to the Print(special file) page — the one where we print a document, and yes, it’s giving main-character energy for your printer 🖨️✨

---

🌸 NAME 🌸

Print — print a document. periodt 💅

---

✨ SYNOPSIS ✨

[file] Print(in mediaType contents,
        in boolean inquisitive,
        in boolean covert
        [in title docName]);

---

💖 DESCRIPTION 💖

okay so the Print request causes the handler to print a document. The handler must act as if the user had issued, via the handler's user interface, either a Print One or Print... command — which one depends on the value of the inquisitive argument. no cap, that’s the vibe check 🫶

The contents argument is the contents of the document. If this argument is unset — in other words, it has a value of (char *)0 — then the contents of the document are in the file named in the message's file attribute. 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. lowkey important, bestie 📝

The inquisitive argument is a boolean value indicating whether the handler is allowed to block on user input while carrying out the request. However, even if inquisitive is True, the handler is not required to seek such input. so it may ask, not must ask — got it? 👑

The covert argument is a boolean value indicating whether the handler may make itself apparent to the user as it carries out the request. If False, the recipient need not make itself apparent. stealth mode-ish, but make it legal 🕵️‍♀️

If both the inquisitive argument and the covert argument are True, the recipient should attempt to limit its presence to the minimum needed to receive any user input desired; for example, through iconification. tiny window energy, iconic 🎀

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. This string would be suitable for display in a window title bar, for example. title-bar-ready, literally 💅

---

🛠️ APPLICATION USAGE 🛠️

The ttmedia_ptype_declare(3) function can be used to register for, and help process, this message. slay, registration handled ✨

This message can be sent with the ttmedia_load(3) function. send it, bestie 📨

---

🌈 EXAMPLES 🌈

To print a PostScript document, the application can send a request of the form:

Print(in PostScript contents,
        in boolean inquisitive,
        in boolean covert);

with a first argument whose value is a vector of bytes such as:

%!0inch {72 mul} def...

The 0fP in the example represents the newline character. The notation is the same as in the ISO C standard. cute newline notation, no cap 😭

To print a PostScript document contained in a file, the application can send the Print request as above, with the file attribute set to the relevant file and with the value of the first argument not set. file-based print request, periodt 📁

---

💀 ERRORS 💀

The ToolTalk service may return one of the following errors in processing the Print request:

• TT_DESKTOP_ENOENT — the file that was alleged to contain the document does not exist.
• TT_DESKTOP_ENODATA — the in-mode contents argument had no value and the file attribute of the message was not set.
• TT_MEDIA_ERR_FORMAT — the document is not a valid instance of the media type.

not the error era, but at least you know what’s up 🚨

---

🦋 SEE ALSO 🦋

• ttmedia_ptype_declare(3)
• ttmedia_load(3)
• Intro
• Status requests

go read those too, iykyk 📚💖

---

cute sign-off for the Print(special file) page, bestie — source/version + date footer energy, and that’s a wrap 🫶💅