On Tue, Jul 05, 2011 at 10:24:18PM -0500, David Champion wrote: > So that's why you need copiousoutput for viewing automatically when > reading a message (vs. from the attachment menu). You didn't say that's > what you're doing, but I imagine it is.
I don't want it to open automatically in my browser whenever a message has an HTML part - I want to hit enter on the message in the attachment list and *then* select it. My point is that mutt's error message "mailcap entry for type text/html not found" (when copiousoutput is not set) is confusing -- I do in fact have an entry for text/html, though it's possible that mutt doesn't like it. I did read the bit in TFM about this, and based on what I was reading, I would have thought that I wanted the *absence* of copiousoutput, since I only want to view the message in the external program when I specifically select it from the attachments menu. Once copiousoutput is set, without any other changes, mutt will attempt to open a file when I select it from the attachment menu (though with the problem mentioned below, i.e., it exits and mutt removes the temporary file), but also seems to try to open all of the attached html files at once when I *reply* to a message. > You also wrote: > > mutt does try to open the file in Firefox on my Mac, but the file it > > passes in doesn't actually exist) > > That's a standard issue with OSX "open". It launches applications > asynchronously and exits, whereupon mutt removes the temporary file. > Then the app finishes launching/receiving remote instruction and looks > for the file, and it's not there. So basically, yes you need a wrapper > script (or an alternate implementation of "open"). I figured it was something like this. What's odd, though, is that opening an attached PDF using "/usr/bin/open %s" works just fine. w
