Re: Include message attributes in print_command?

On Sat, Jan 10, 2009 at 03:27:56PM -0500, Ed Blackman wrote: > I use Mutt on Linux, and use enscript to print to my cups-pdf printer: >set print_command="enscript --highlight=mail -P ToPDF" > > This produces a PDF named Enscript_Output.pdf in ~/PDF when I print. > > However, "Enscript_Output"

Re: mutt 1.5.19: Segmentation fault

On Wednesday, 07 January 2009 at 20:02, Tobias Mummert wrote: > * Brendan Cully [2009-01-07 03:25 CET]: > > > Er. That wasn't supposed to fix it, it was just supposed to improve > > the backtrace. Possibly the make clean alone did the trick -- you > > could make clean and make and see if it contin

Include message attributes in print_command?

I use Mutt on Linux, and use enscript to print to my cups-pdf printer: set print_command="enscript --highlight=mail -P ToPDF" This produces a PDF named Enscript_Output.pdf in ~/PDF when I print. However, "Enscript_Output" isn't very descriptive, and if I print one message, then print another,

Different $date_format in $index_format and $attribution

Hi List, I'd like to have date_format="%d/%b %H:%M" in the message index and a more detailed one (date_format="!%a, %b %d, %Y at %I:%M:%S%p %Z") in the $attribution. I tried this: folder-hook . 'set date_format="%d/%b %H:%M"' reply-hook . 'set date_format="!%a, %b %d, %Y at %I:%M:%S%p %Z"' but I