On Wed, Mar 31, 2010 at 09:44:09AM +1100, Cameron Simpson wrote: > On 30Mar2010 11:11, Nicolas Williams <[email protected]> wrote: > | On Tue, Mar 30, 2010 at 10:43:08AM -0500, Nicolas Williams wrote: > | > On Tue, Mar 30, 2010 at 07:04:22PM +1100, Cameron Simpson wrote: > | > > If I complete the reply immediately (as now), it's all seamless. > | > > > | > > But if I want to defer the reply for later, I simply detach from screen > | > > and reattach later. Here's this message in progress: > | > > | > But what happens on detach in the parent mutt (edit abort?)? (I've > | > tried it, and the screen does not appear to start. > | > | Oh, I got it to work. I needed to insert "env TERM=xterm-color" into > | the screen command-line (I'd completely forgotten). > > That's surprising; it suggests your $TERM isn't set up right outside > mutt.
It's a terminfo / libslang issue. > | screen -ls output > | gets mangled, but that's screen's fault: > | There are screens on: > | [...] > | 3820.mutt-30mar2010-11:06 Re_Foobars_Request_1 (Detached) > > Cool. So, working for you now? Turns out I can screen -r <pid>, so, yes. > Glad to here it. Any specific problems remaining to address? The replied flag issue. The connection sharing and password caching issues. I can live. (Actually, _I_ don't need this, as I'm happy to postpone messages when I need to switch gears. But I know of at least one user who desperately needs a new MUA but will not adopt mutt because of this missing feature.) Nico --
