On Sun, Sep 20, 2009 at 11:01:26PM +1000, Cameron Hutchison wrote: > In the previous version of mutt, I could > a) v (to show all attachments), > b) select the attachment with arrow keys > c) press enter > > This would cause mutt to use the system mailcap to invoke an external > program to handle the attachment. The mailcap entry used would not have > been the one marked with copiousoutput. > > I would use this to view html attachments with lynx interactively. Right > now, the only way to view an html attachment interactively would be to > do as you have said and run "| lynx". This is a backwards step. > > Even with the proposed fix to not handle text/html internally, what > happens to other text/* mime types that were previously handled with an > external viewer? > > The purpose of mailcap is so that it can specify the program to use. > Having to run "| program" means there may as well not be any mailcap > functionality at all. > > The problem with auto_view is that it favours the mailcap entry with > copiousoutput. This does not allow for using an external program > interactively. >
Hi Cameron, if your problem happens with html or other non-human readeable format which are marked as text/*, I'm working on a patch which will exclude them from the internal viewer and will restore the previous behavior. For other human-readeable format like text/plain we would like to keep this behavior, i.e.: using the internal viewer, does this make sense to you? Cheers Antonio -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
