TTDT_REVERT(3)

🌸 NAME: ttdt_Revert(library call) 🌸

Okay bestie, the header energy is literally ttdt_Revert(library call), and this function is here to request a ToolTalk client to revert a file — like “bestie, please discard the pending changes” but in ToolTalk 💖.

---

🦋 SYNOPSIS 🦋

#include &<Tt/tttk.h>
Tt_status ttdt_Revert(
Tt_message context,
const char *pathname,
Tt_scope the_scope,
XtAppContext app2run,
int ms_timeout);

---

💅 DESCRIPTION 💅

So ttdt_Revert sends a Revert request in the the_scope argument and waits for the reply. A Revert request asks the handling ToolTalk client to discard any changes pending on pathname. That’s the assignment, no cap.

The context argument describes the environment to use. If context is not zero, messages created by ttdt_Revert inherit from context all contexts whose slotname begins with the characters ENV_.

The the_scope argument identifies the scope of the request. If the_scope is TT_SCOPE_NONE, ttdt_Revert tries TT_BOTH, and falls back to TT_FILE_IN_SESSION if, for example, the ToolTalk database server is not installed on the file server that owns pathname. Resilient queen behavior, honestly.

The ttdt_Revert function passes app2run and ms_timeout to tttk_block_while(3), blocking on the reply to the Save request it sends. Yes, the page says Save right there — I’m keeping the lore exactly as written 😭.

---

🎀 RETURN VALUE 🎀

Upon successful completion, the ttdt_Revert function returns the status of the operation as one of the following Tt_status values — periodt:

• TT_OK — the sent request received an affirmative reply within ms_timeout milliseconds. Slay.
• TT_DESKTOP_ETIMEDOUT — no reply was received within ms_timeout milliseconds.
• TT_DESKTOP_EPROTO — the request was failed, but the handler set the tt_message_status of the failure reply to TT_OK, instead of a specific error status. Rude, but noted.
• TT_ERR_DBAVAIL — the ToolTalk service could not access the ToolTalk database needed for this operation.
• TT_ERR_DBEXIST — the ToolTalk service could not access the specified ToolTalk database in the expected place.
• TT_ERR_NOMEM — there is insufficient memory available to perform the function.
• TT_ERR_NOMP — the ttsession(1) process is not running and the ToolTalk service cannot restart it.
• TT_ERR_OVERFLOW — the ToolTalk service has more active messages than it can handle. (The maximum number of active messages is implementation specific, but is at least 2000.)
• TT_ERR_POINTER — the pathname argument was NULL or was a ToolTalk error pointer.
• TT_ERR_PROCID — the specified process identifier is out of date or invalid.

---

🔥 SEE ALSO 🔥

• Tt/tttk.h - Tttttk(5), ttdt_Save(3), ttdt_file_join(3), ttdt_file_event(3), tttk_block_while(3).

---

Okay bestie, that’s the whole page! The footer vibe is ttdt_Revert(library call) — that’s the library-call source/version stamp, and there’s no date in the original footer, so we are not inventing one 🫶💅✨