Every once in a while (like every year) I get a message that completely
fracs up mutt's access to my mailbox (IMAP). Or some sequence of events
corrupts a message to manifest this problem. Mutt parses my entire
mailbox, and then at the end it completely fails to open it. However,
there is no pro
=- Dave Burns wrote on Tue 29.Apr'08 at 11:27:11 -1000 -=
> echo 'test email using mutt'|mutt -s 'test email using mutt'
>
>
> it hangs up for a while (can't interrupt it with cntl-c or background
> it with cntl-z and bg) and then produces this error message:
>
> fcntl: No locks available (
=- Wilkinson, Alex wrote on Wed 30.Apr'08 at 8:36:04 +0800 -=
> >> Is it possible to stop threads un-collaping as new mail
> >> arrives ?
> >
> >Yes, check vars with "collapse" in them.
>
> Ok, filtering on the word "collapse" in the manual all I come up with is:
>
>3.28. collapse_unread
>
Hi,
I have this in my .muttrc
color body blueblack "((To:) .*)|((Cc:) .*)"
This does the job for one line. But most of the times To / Cc will be
extending to next 2-3 line due to long listings of names.
Is there a way to color entire To/Cc field list ?
- Ravi
Maybe I was not clear. I don't want my sent messages to be saved. I
want a cron job to be able to send email with attachments, which mutt
does nicely.
On Wed, Apr 30, 2008 at 9:29 AM, Rado S <[EMAIL PROTECTED]> wrote:
> =- Dave Burns wrote on Tue 29.Apr'08 at 11:27:11 -1000 -=
> > echo 'test ema
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday, April 30 at 03:31 PM, quoth Ravi Uday:
>Hi,
>
>I have this in my .muttrc
>
>color body blue black "((To:) .*)|((Cc:) .*)"
>
>This does the job for one line. But most of the times To / Cc will be
>extending to next 2-3 line
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday, April 30 at 12:40 PM, quoth Dave Burns:
> Maybe I was not clear. I don't want my sent messages to be saved. I
> want a cron job to be able to send email with attachments, which mutt
> does nicely.
Ah! Well then. Add this to the relevan
