Re: Mark threads as read for the future

2016-04-21 Thread Andreas Doll
On 2016-04-14 at 18:15, Francesco Ariis wrote: > I wrote a small folder-hook pattern which accomplishes a similar task > (deletes instead 'mark as read') [1]. I suspect it can be modified to > suit your needs (tag-pattern + tag-prefix maybe?). > Fire again if you need help > [1] http://ariis.it/sta

Re: Do not spellcheck quoted parts of email

2016-04-21 Thread Xu Wang
On Wed, Apr 20, 2016 at 4:55 PM, Mike K. wrote: > * Xu Wang wrote on 2016-02-20 05:56 +: >>> >>> I use aspell (`aspell -e -d it -c`) and it ignores quoted parts. >> >> >> Thank you for your helps. I now use what follows: >> set ispell='aspell -e -c' > > > Thanks very much for this --- worked a

Re: Show output (and place for extra input) from sendmail command

2016-04-21 Thread Xu Wang
On Wed, Apr 20, 2016 at 6:03 AM, wrote: > On 19Apr2016 20:30, Xu Wang wrote: >> >> I use a custom sendmail command. I would like to have my script (that >> I set to 'sendmail' muttrc variable) ask some questions from to the >> user and also give feedback to the user directly. But mutt does not >

My print command cannot use "read -p"

2016-04-21 Thread Xu Wang
Hi, I would like to have a print command that takes input from the user. But mutt pipes the message to the print command so I guess I cannot use something like read -p "where to save?" filename because read looks on STDIN and mutt already piped to STDIN. I am using bash. Any idea? Kind regards

Re: My print command cannot use "read -p"

2016-04-21 Thread Jon LaBadie
On Fri, Apr 22, 2016 at 12:47:45AM -0400, Xu Wang wrote: > Hi, > > I would like to have a print command that takes input from the user. > But mutt pipes the message to the print command so I guess I cannot > use something like > read -p "where to save?" filename > > because read looks on STDIN an

Re: My print command cannot use "read -p"

2016-04-21 Thread David Champion
* On 21 Apr 2016, Xu Wang wrote: > Hi, > > I would like to have a print command that takes input from the user. > But mutt pipes the message to the print command so I guess I cannot > use something like > read -p "where to save?" filename > > because read looks on STDIN and mutt already piped to

Re: My print command cannot use "read -p"

2016-04-21 Thread Jon LaBadie
On Thu, Apr 21, 2016 at 10:00:08PM -0700, David Champion wrote: > * On 21 Apr 2016, Xu Wang wrote: > > Hi, > > > > I would like to have a print command that takes input from the user. > > But mutt pipes the message to the print command so I guess I cannot > > use something like > > read -p "where