Slow to respond here.
Mutt's MIME handling stuff has a long section in the manual here:
http://www.mutt.org/doc/manual/#mimesupport
with the mailcap section commencing here:
http://www.mutt.org/doc/manual/#mailcap
In particular see the stuff about "copiousoutput" and the pager.
On 12May2022 15:3
On Thu, May 12, 2022 at 08:51:47PM +0100, Chris Green wrote:
> On Thu, May 12, 2022 at 03:38:23PM -0400, Christopher Conforti wrote:
> > Hi list, I'm having a bit of a weird one, at least for me. I can't get mutt
> > to
> > read my entire mailcap file properly, it seems. For example, I have the
>
On Thu, May 12, 2022 at 08:05:52PM +, Sam Kuper wrote:
> On Thu, May 12, 2022 at 03:38:23PM -0400, Christopher Conforti wrote:
> > text/html lynx -dump %s | more
> >
> > is seemingly ignored, even when there are no other options given for
> > handling HTML.
>
> I may be wrong, but shouldn't
On Thu, May 12, 2022 at 03:38:23PM -0400, Christopher Conforti wrote:
> Hi list, I'm having a bit of a weird one, at least for me. I can't get mutt to
> read my entire mailcap file properly, it seems. For example, I have the
> following line in my mailcap:
>
> images/*; eog %s
>
> It handles
On Thu, May 12, 2022 at 03:38:23PM -0400, Christopher Conforti wrote:
> text/html lynx -dump %s | more
>
> is seemingly ignored, even when there are no other options given for
> handling HTML.
I may be wrong, but shouldn't there be a semicolon in that entry? I.e.
text/html; lynx -dump
Hi list, I'm having a bit of a weird one, at least for me. I can't get mutt to
read my entire mailcap file properly, it seems. For example, I have the
following line in my mailcap:
images/*; eog %s
It handles this just fine; all image attachments are opened with eog. However,
another line:
