Antonio Radici wrote: > On Sun, Sep 20, 2009 at 10:13:11PM +1000, Cameron Hutchison wrote: > > A further consequence of this text/* change seems to be that I cannot > > invoke an interactive viewer on any text/* attachments. Either it is > > handled internally, or flagged with auto_view, in which case, only > > mailcap entries with copiousoutput are used. > > > > How do I disable the internal viewer without using auto_view? > > To disable the internal viewer you need to use auto_view, as specified > in the patch and the it will follow the mailcap actions; if you do want > to use a different viewer I suppose that piping attachments to your > preferred interactive viewer should work, what I would do is, from the > message view: > a) v (to show all attachments), > b) then I select the attachment with the arrow keys w/out pressing enter > c) | less (or | vim -), which will invoke less or vim > > Does this answer your question?
The question was more to demonstrate the problem. 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. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
