On Sun, Oct 15, 2000 at 05:11:47PM +0100 or so it is rumoured hereabouts,
Dan Boger thought:
> On Sun, Oct 15, 2000 at 12:51:12PM +0100, Conor Daly wrote:
> > I don't think this would work. mutt sits waiting for the editor to
> return
> > before sending the mail. If you use gvim which detaches itself from
> mutt,
> > mutt decides that you've abandoned the message and aborts the send.
> To
> > make mutt use gvim you need to use something like
> >
> > set editor='gvim -e'
> >
> > which tells gvim to remain within the current process until it exits
> > rather than detaching from its parent immediately.
>
> ok, but that doesn't help you keep reading mail while you're editing a
> draft...
> I don't have a solution for this though - need some way for mutt to just
> go
> on, not waiting for the process, and not deleteing the tmpfile... then,
> somehow,
> when the editor is done, something needs to send that mail...
>
Exactly my point...
could do something like
set edit_hdrs
set editor='independent-process-and-send-script &'
and have independent-process-and-send-script look something like
#!/bin/bash
gvim -e $1
mutt -s<Subject somehow gathered from mutt> <recipient also gathered from mutt> < $1
# END
There was mention of how to get the recipient and subject from mutt with
vim in another thread here.
That would do it...
--
Conor Daly <[EMAIL PROTECTED]>
Domestic Sysadmin :-)
