Re: Mailcap selectively applying settings
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 this just fine; all image attachments are opened with eog. However, > another line: > > text/html lynx -dump %s | more > I think you need:- text/html; lynx -dump %s; copiousoutput; nametemplate=%s.html > is seemingly ignored, even when there are no other options given for handling > HTML. No matter which browser I set, no matter what combination of options I > use, I cannot seem to get mutt to use this entry in any way. By all clues in > the > documentation, my personal mailcap file (~/.mailcap) should take priority, but > it only seems to want to set for certain types. > > What the heck is going on? Where can I learn how to fix it? I think the 'copiousoutput' is explained somewhere on the Mutt web site. -- Chris Green
Re: Mailcap selectively applying settings
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 %s | more If that doesn't help, please unpack what you mean by "seemingly ignored". E.g. give steps to reproduce the problem. That might help someone on this list get a better handle on troubleshooting with you. Sam -- A: When it messes up the order in which people normally read text. Q: When is top-posting a bad thing? () ASCII ribbon campaign. Please avoid HTML emails & proprietary /\ file formats. (Why? See e.g. https://v.gd/jrmGbS ). Thank you.
Mailcap selectively applying settings
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: text/html lynx -dump %s | more is seemingly ignored, even when there are no other options given for handling HTML. No matter which browser I set, no matter what combination of options I use, I cannot seem to get mutt to use this entry in any way. By all clues in the documentation, my personal mailcap file (~/.mailcap) should take priority, but it only seems to want to set for certain types. What the heck is going on? Where can I learn how to fix it? -- Christopher Conforti signature.asc Description: PGP signature
Re: New to Mutt, unable to send messages in *any* attempted way
On Wed, May 11, 2022 at 09:51:28PM +0100, Sam Kuper wrote: > Once you know your shell's quoting syntax, you will see that you can > probably achieve your goal in any of several different ways. Which to > use is a matter of taste. > > E.g. > > '/home/.user.gpg' > > vs > > "~"'/.user.gpg' Sorry, my first example above should have been: '/home//.user.gpg' -- A: When it messes up the order in which people normally read text. Q: When is top-posting a bad thing? () ASCII ribbon campaign. Please avoid HTML emails & proprietary /\ file formats. (Why? See e.g. https://v.gd/jrmGbS ). Thank you.
