Re: saving messages to a file

2002-01-24 Thread David T-G
Richard -- ...and then Richard G. Ball said... % % On [2002-Jan-23] David Champion <[EMAIL PROTECTED]> wrote: % > % > Looks like your push sequence is just appending to the default name % > already in the edit buffer. One way around this would be just to put a % > as the first binding after t

Re: saving messages to a file

2002-01-23 Thread Richard G. Ball
On [2002-Jan-23] David Champion <[EMAIL PROTECTED]> wrote: > > Looks like your push sequence is just appending to the default name > already in the edit buffer. One way around this would be just to put a > as the first binding after the ";s". That does it very nicely, thanks! Rich

Re: saving messages to a file

2002-01-23 Thread David Champion
On 2002.01.23, in <[EMAIL PROTECTED]>, "Richard G. Ball" <[EMAIL PROTECTED]> wrote: > > #!/bin/sh > mutt -nz -F $HOME/.mutt/mutt.archiving -f test-folder -e "push 'T~d -01/01/02 > ;s archivetest > q'" > > but it isn't *quite* working. The file to which the messages are > written isn't ar

saving messages to a file

2002-01-23 Thread Richard G. Ball
I poked around in the archives and found a simple recipe for saving old messages that could be run from a command line/script. My version of this became: #!/bin/sh mutt -nz -F $HOME/.mutt/mutt.archiving -f test-folder -e "push 'T~d -01/01/02 ;s archivetest q'" but it isn't *quite* working. The