]
Subject: Re: Composing a draft?
Reply-To: Suresh Ramasubramanian [EMAIL PROTECTED]
Mail-Followup-To: MUTT Users [EMAIL PROTECTED]
User-Agent: Mutt/1.2.5i
Organization: The Lumber Cartel, India (tinlcI)
Bob Bell proclaimed on mutt-users that:
Just open another mutt session. Unlike many
On Sun, Oct 15, 2000 at 10:20:06AM +0530, Suresh Ramasubramanian muttered:
Bob Bell proclaimed on mutt-users that:
Just open another mutt session. Unlike many mail editors, you can
have multiple instances of mutt running at the same time.
However, mailbox flags get modified when you
On Sun, Oct 15, 2000 at 10:20:06AM +0530 or so it is rumoured hereabouts,
Suresh Ramasubramanian thought:
Bob Bell proclaimed on mutt-users that:
Just open another mutt session. Unlike many mail editors, you can
have multiple instances of mutt running at the same time.
However,
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
Dan Boger [EMAIL PROTECTED] wrote on Sun, 15 Oct 2000:
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...
Well, the answer is
On Sun, Oct 15, 2000 at 10:13:00PM +0530, Suresh Ramasubramanian wrote:
Charles Curley proclaimed on mutt-users that:
Which is rather useless because then mutt just sits there with its tongue
hanging out saying "Waiting for Emacs..." until the editor completes. That
phrase is probably
On Sun, Oct 15, 2000 at 10:20:06AM +0530, Suresh Ramasubramanian wrote:
Bob Bell proclaimed on mutt-users that:
Just open another mutt session. Unlike many mail editors, you can
have multiple instances of mutt running at the same time.
However, mailbox flags get modified when you do
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
Conor Daly [EMAIL PROTECTED] wrote on Sun, 15 Oct 2000:
mutt -sSubject somehow gathered from mutt recipient also gathered from mutt $1
It might be easier to just use "mutt -H tempfile", and then use /dev/null
as the input.
Mikko
--
// Mikko Hänninen, aka. Wizzu // [EMAIL PROTECTED] //
why not just sync the mailbox before starting the draft? then if you start
another mutt which modifies the flags, it doesn't matter.
peter
On 15 Oct 00, 12:16PM, Dan Boger wrote:
On Sun, Oct 15, 2000 at 12:51:12PM +0100, Conor Daly wrote:
I don't think this would work. mutt sits waiting for
clever!
On 15 Oct 00, 8:23PM, Ulf Erikson wrote:
There is a nice (or at least fun) fix for this at
http://www.robots.ox.ac.uk/~neil/mutt/
The idea is to use a small script, which returns immediately, as editor;
this script will spawn a new instance of mutt, running in a term of its own,
On Sat, Oct 14, 2000 at 06:56:40PM +0800, Anthony Liu [EMAIL PROTECTED] wrote:
Is there a way to tell mutt that I am composing a draft without
finishing the editing and do the postpone action? If this is
possible, I would like to spawn another terminal (or even an X-based editor)
for the
Bob Bell proclaimed on mutt-users that:
Just open another mutt session. Unlike many mail editors, you can
have multiple instances of mutt running at the same time.
However, mailbox flags get modified when you do this - especially with mbox
folders. A better thing to do is to use
13 matches
Mail list logo
