Repository navigation
Quit: hold the quit while a send runs, so text typed during a slow send is saved #206
Description
Problem
A normal quit or a window close waits up to 1.5 s for the window to save its drafts (FLUSH_WAIT in src-tauri/src/studio/quit.rs). The window first waits for each send on its way, then saves each changed screen. During a send, the window does not save the screen it is sending from. If that save ran, the screen's draft would have two owners: the send, and the save.
So if a send takes longer than 1.5 s, text the person typed during it is lost when the quit goes through. A send normally ends in milliseconds. It runs longer only when copying large pictures, or while it waits for the update pass.
#201 ships with this as a known limit. A fix that saved during the send was tried in 964383e and reverted. It kept one draft under two screens, and it brought a sent picture back after a relaunch (#205).
Fix
Rust holds a quit for as long as a send runs, then gives the window its 1.5 s to save. The window would tell Rust when a send starts and ends, and the quit hold in quit.rs would wait on that before its timer starts. Keep a ceiling, so a hung send cannot block a quit forever.
Test
A window test with a held send, text typed during it, and a quit. The text is saved once, under its own screen, after the send answers. A Rust test checks that the hold waits for a send in flight and still ends at its ceiling.
Activity
pullfrog commentedon Nov 8, 2026
Implementation plan
QuitFlush::holdcurrently emitsstudio://flushand starts the 1.5 s timeout immediately. Studio drafts: one owner for the draft and the outgoing message #205 is related but explicitly excludes the quit wait; it is not a duplicate.gpt-6.1-terra｜ 𝕏fix(studio): the cleanup keeps a cut-off first send's pictures, and a…
fix(studio): a send takes what was clicked, a quit loses no draft, an…