On 19 Mar 2008 14:22 -0700, by harrelson@xxxxxxxxx (Culley Harrelson): > I am ready to tackle this problem but when you pipe a message to a > script it looks like a new process is spawned and the new process > can't remain in control of the terminal. Can anyone point me in the > right direction to make this happen? I'm not sure I see what you mean. I just tried piping a message into 'less' with a /dev/null muttrc, and had no problems at all with it retaining control of the terminal for as long as I wanted it to. -- Michael Kjörling .. michael@xxxxxxxxxxx .. http://michael.kjorling.se * ..... No bird soars too high if he soars with his own wings ..... * * ENCRYPTED email preferred -- OpenPGP key ID: 0x 758F8749 BDE9ADA6 * * ASCII Ribbon Campaign: Against HTML mail, proprietary attachments *
Attachment:
signature.asc
Description: Digital signature