Yes, of course my suggestion is just a temporary fix. As soon as update-mime is rerun, /etc/mailcap is over written. The best fix would be if the unzip and tar packages did not come with mime entries in /usr/lib/mime/packages/.
Unfortunately, it seems a local administrator has no way to make a permanent fix in Debian. The order of entries can be changed with mailcap.order, but that does not appear to do what we want, which is to remove all mailcap entries for the archive mimetypes. Please let me know if I am wrong about this. --Ben On Wed, Jan 2, 2013 at 12:13 PM, Vincent Lefevre <vinc...@vinc17.net> wrote: > On 2013-01-02 11:04:35 -0800, Ben Wong wrote: > > Fortunately, a quick fix (at least for w3m) is easy. One can comment out > > the broken lines in /etc/mailcap: > > > > # It is better to not pretend to know how to deal with archives. > > #application/x-tar; /bin/tar tvf -; print=/bin/tar tvf - | print > > text/plain:-; copiousoutput > > #application/x-gtar; /bin/tar tvzf -; print=/bin/tar tvzf - | print > > text/plain:-; copiousoutput > > #application/zip; unzip -l '%s'; nametemplate=%s.zip; copiousoutput > > > > I'm sure there's a more correct fix, but I'd be surprised if this patch > > causes any problems. > > This may cause problems when upgrading or removing packages. > There may be alternate workarounds; see the mailcap.order(5) > man page. > > -- > Vincent Lefèvre <vinc...@vinc17.net> - Web: <http://www.vinc17.net/> > 100% accessible validated (X)HTML - Blog: <http://www.vinc17.net/blog/> > Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon) >
