From mutt-users Wed Nov 08 15:15:26 2006 From: Marco Fioretti Date: Wed, 08 Nov 2006 15:15:26 +0000 To: mutt-users Subject: Fwd: Re: How to make mutt execute commands from the command line? Message-Id: <1.3.200611081615.98043 () mclink ! it> X-MARC-Message: https://marc.info/?l=mutt-users&m=116299916820588 MIME-Version: 1 Content-Type: multipart/mixed; boundary="-----_____________20061108161598043.mclink.it--" This is a multi-part message in MIME format. Questo e' un messaggio multi parte in formato MIME. -----_____________20061108161598043.mclink.it-- Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit posting to the list after Nicolas pointed out I had used the wrong reply address, answering only to him. Sorry, right now I can only use webmail, not mutt, to communicate, and it's very painful. Marco -----_____________20061108161598043.mclink.it-- Content-Type: message/rfc822 Content-Transfer-Encoding: 7bit Content-Disposition: inline From: Marco Fioretti To: Subject: Re: How to make mutt execute commands from the command line? Date: Wed, 08 Nov 2006 15:49:16 +0100 Message-Id: <1.3.200611081549.56850@mclink.it> MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit X-Mailer: Easy-MAIL v1.3 - http://www.mclink.it/ Nicolas Rachinsky wrote: > * Marco Fioretti [2006-11-08 15:07 +0100]: > > mutt -f test_in -e 'tag-pattern>.test_out/' > > -e needs an configuration file command, so you should prepend > a push and the missing <). Then this or something similar should work. Oh man! I knew it was something silly. I _had_ tried the missing < earlier, but I had also completely overlooked the "push" part... Thanks! Now, if I run this (test_mbox is in mbox format): mutt -m Maildir -f test_mbox -e 'push .test_out' mutt does what I want, that is: open test_mbox tag all messages copy all of them to test_out, in Maildir format Two final questions/confirmations: 1) Mutt beeps when starting and remains open after copying the messages. This is a sure sign that the '' part is wrong, but I don't recognize in the manual any clue on how to make it quit as soon as it has copied everything to the new maildir... (remember this should eventually run unattended inside a bash loop) For the record, if I hit q manually, it does quit without asking for confirmation 2) from a partial inspection, it looks like all the status (new, read, unread) and other flags are left unchanged, in both the original and destination mailbox, which is just what I want. The question is, this _is_ what is guaranteed to always happen with that macro, isn't it? Or maybe it happened in this test because of some weird configuration variable? Thanks again for your lightning fast support! Marco -----_____________20061108161598043.mclink.it----