Re: Composing a draft?
If all you want to do is _read_ a few messages without modiying flags, just access the folder in read-only mode. On 2000-10-15 10:20:06 +0530, Suresh Ramasubramanian wrote: Date: Sun, 15 Oct 2000 10:20:06 +0530 From: Suresh Ramasubramanian [EMAIL PROTECTED] To: MUTT Users [EMAIL PROTECTED] 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 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 something like gvim or emacs as the editor (both of which pop up in different terms from the mutt window, and multiple sessions of which can be opened leaving your mutt xterm free) Of course, on a console, this means some tedious shifting between alt-f1, alt-f2 ... virtual consoles ;) -- Suresh Ramasubramanian + Wallopus Malletus Indigenensis mallet @ cluestick.org + Lumber Cartel of India, tinlcI Azh nazg durbataluk, azh nazg gimbatul, Azh nazg thrakataluk agh burzum ishi krimpatul -- Thomas Roessler [EMAIL PROTECTED]
Re: Composing a draft?
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 do this - especially with mbox folders. A better thing to do is to use something like gvim or emacs as the editor (both of which pop up in different terms from the mutt window, and multiple sessions of which can be opened leaving your mutt xterm free) 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 an artifact of emaclient rather than mutt, but it does reneder mutt rather useless while one is editing an email. -- -- C^2 No windows were crashed in the making of this email. Looking for fine software and/or web pages? http://w3.trib.com/~ccurley PGP signature
Re: Composing a draft?
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, mailbox flags get modified when you do this - especially with mbox folders. A better thing to do is to use something like gvim or emacs as the editor (both of which pop up in different terms from the mutt window, and multiple sessions of which can be opened leaving your mutt xterm free) Of course, on a console, this means some tedious shifting between alt-f1, alt-f2 ... virtual consoles ;) 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. -- Conor Daly [EMAIL PROTECTED] Domestic Sysadmin :-)
Re: Composing a draft?
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... -- Dan Boger System Administrator [EMAIL PROTECTED] PGP signature
Re: Composing a draft?
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 "multi-threading", something that the current Mutt doesn't do, and which would be a fairly significant change in the program structure. I suppose it could be kludged in to work even without multi-threading, but that wouldn't be the "right" solution IMHO. Mikko -- // Mikko Hänninen, aka. Wizzu // [EMAIL PROTECTED] // http://www.iki.fi/wiz/ // The Corrs list maintainer // net.freak // DALnet IRC operator / // Interests: roleplaying, Linux, the Net, fantasy scifi, the Corrs / binary tree n.: see binary tree and binary tree.
Re: Composing a draft?
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 an artifact of emaclient rather than mutt, but it does reneder mutt rather useless while one is editing an email. Sounds like a nice thing to fix ;) 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, ready to compose a mail from your half-made mail as a template. You can easily modify the script to work without the xterm-title patch. Ulf
Re: Composing a draft?
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 this - especially with mbox folders. A better thing to do is to use something like gvim or emacs as the editor (both of which pop up in different terms from the mutt window, and multiple sessions of which can be opened leaving your mutt xterm free) Of course, on a console, this means some tedious shifting between alt-f1, alt-f2 ... virtual consoles ;) The problem is mutt will still wait for the editor to finish because mutt will only determine it is a draft when you exit the editor and hit the postpone key. If there is a way to tell mutt not to wait (just start the editor in another thread and handle the draft file), then it is possible to edit a long draft and read other mails at the same time. For the time being, starting another copy of mutt is half a solution. I can think of another solution: create a script that can handle the draft file directly without help from mutt. It will take the draft file, parse it, take the contents out to a temp file, start the editor with the temp file. When editing is done, it will load the temp file back to the draft file and modify the draft file headers and put them back altogether.
Re: Composing a draft?
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 -sSubject 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 :-)
Re: Composing a draft?
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] // http://www.iki.fi/wiz/ // The Corrs list maintainer // net.freak // DALnet IRC operator / // Interests: roleplaying, Linux, the Net, fantasy scifi, the Corrs / God is REAL, unless explicitly declared INTEGER.
Re: Composing a draft?
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 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... -- Peter Jaques [EMAIL PROTECTED] http://cs.oberlin.edu/~pjaques klezmerbalkanturkish clarinet; free foodshelter; books to prisoners pgp: email me with subject "get pgp key", or finger [EMAIL PROTECTED]
Re: Composing a draft?
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, ready to compose a mail from your half-made mail as a template. You can easily modify the script to work without the xterm-title patch. Ulf
Composing a draft?
Hi everyone, 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 editor so I can read other mails while composing a draft? In other words, I prefer the editor not to tie up mutt while composing mail. Any ideas?
Re: Composing a draft?
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 editor so I can read other mails while composing a draft? In other words, I prefer the editor not to tie up mutt while composing mail. Just open another mutt session. Unlike many mail editors, you can have multiple instances of mutt running at the same time. -- Bob Bell [EMAIL PROTECTED] - "Microsoft has never been an innovator - it's a fast follower. And when you're as big and dominant as Microsoft, and growing at 30 or 40 percent a year, it gets harder and harder to find people to be fast followers of." -- Paul Saffo, Institute for the Future
Re: Composing a draft?
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 something like gvim or emacs as the editor (both of which pop up in different terms from the mutt window, and multiple sessions of which can be opened leaving your mutt xterm free) Of course, on a console, this means some tedious shifting between alt-f1, alt-f2 ... virtual consoles ;) -- Suresh Ramasubramanian + Wallopus Malletus Indigenensis mallet @ cluestick.org + Lumber Cartel of India, tinlcI Azh nazg durbataluk, azh nazg gimbatul, Azh nazg thrakataluk agh burzum ishi krimpatul
