Re: Wish: -r option to recover a crashed session
On 01:21 09 Jul 2004, Gary Johnson <garyjohn@xxxxxxxxxxxxxxx> wrote:
| On 2004-07-09, Cameron Simpson <cs@xxxxxxxxxx> wrote:
| > On 21:59 05 Jul 2004, Gary Johnson <garyjohn@xxxxxxxxxxxxxxx> wrote:
| > | On 2004-07-05, "Roy S. Rapoport" <mutt-users@xxxxxxxxxxxxxxxxx> wrote:
| > | > Dude, Mun Johl seems to specifically address _mutt_ dying.
| > | In his original posting he began,
| > | There are times when I'm going through my mbox and I have
| > | deleted items, applied labels, etc. and before I sync up the
| > | file I loose my network connection for some reason.
| > |
| > | So while he was asking for a solution to the general problem of mutt
| > | dying, his specific problem seemed to be that his network connection
| > | was dropping.
| >
| > Then he's probably getting a SIGHUP as his terminal hangs up.
| >
| > Sounds like one route would be to give mutt a
"sync--and-quit-on-HUP-or-TERM"
| > switch, defaulting to on. Thoughts?
|
| That would update the state of the current folder before mutt
| stopped, but it wouldn't save anything else about the state of mutt
| before it stopped, which may or may not be OK.
It's enough for his description above, but you have a point.
Still, it would go a long way to addressing his issue.
| If the user was in
| the compose menu, for example, nothing about the message being
| composed would be saved. I'm not sure what would happen if the user
| was editing a message when SIGHUP was generated.
|
| So my thought is that a "sync--and-quit-on-HUP-or-TERM" switch
| wouldn't be enough to avoid frustrating data loss upon an unexpected
| hang-up.
Well I see two approaches to this, one already ok.
Firstly, editors tend to save interrupted sessions. So that's so of ok.
Second, when I abort a mutt compose session it asks if I want the message
postponed. Have any message in compose mode _be_ in the postponed queue,
and have that question undo that state if necessary. In this way the
compose state is covered too.
Sound ok?
--
Cameron Simpson <cs@xxxxxxxxxx> DoD#743
http://www.cskk.ezoshosting.com/cs/