SAVE(4)

💾 NAME 💾

Save — save any modifications to an entity. This is the Save(special file) page, bestie — special-file manual name, folded in right here like a little name tag. 💅

✨ SYNOPSIS ✨

[file] Save(in type ID);

🦋 DESCRIPTION 🦋

okay so the Save notice asks that any pending, unsaved modifications to a persistent entity (such as a file) be saved. no cap.

The ID argument is the identity of the entity to save. When its type is File, then the ID argument is unset (in other words, has a value of (char *)0), and it refers to the file or directory named in the message's file attribute. 🫶

💀 ERRORS 💀

The ToolTalk service may return one of the following errors in processing the Save notice:

• TT_DESKTOP_UNMODIFIED — The entity had no pending, unsaved modifications. 💀
• TT_DESKTOP_ENOENT — The file to save/revert does not exist. 😭

🌸 APPLICATION USAGE 🌸

• The ttdt_file_join(3) function can be used to register for, and help process, the Save request. ✨
• The Save request can be sent with ttdt_file_request(3). Also, ttdt_Save(3) can send the relevant message and block on the reply. 🔥

👑 SEE ALSO 👑

ttdt_Save(3), ttdt_file_join(3), ttdt_file_request(3); Revert notice. 🦋

mwah 💋 — that's the Save(special file) manual page, and the footer has no extra source/version or date info, so I'm not making one up, periodt. 🎀