Alexander Zangerl writes: > On Thu, 29 Oct 2015 17:34:43 +0100, Harald Geyer writes: > >The actual problem: > >When I mhshow a message with a text/html part on the linux virtual > >terminal, the current mhn.defaults invokes "run-mailcap --action=view", > >which in turn invokes sensible-browser, which on my system happens to > >produce output not suitable for display in a pager - ie lots of > >escape sequences. > > the fact that run-mailcap may or may not produce ideal output for terminal > or paged use isn't nmh's problem.
I think correctly using run-mailcap semantics is nmh's problem: "run-mailcap --action=view" is meant to start a pager, which is not what mhshow wants to do. mhshow wants formatted output that can be passed on to it's own pager (moreproc). There is a way to get the output expected by mhshow: run-mailcap --action=cat > i most definitely don't want nmh to depend on particular browsers > or blob viewers, so i set the default mhn.defaults to the really > low common denominator of run-mailcap. Agreed. > as this is just the default mhn config, nothing keeps people from > overriding this with their personal variations that are finetuned for > x/console/whatever use. Actually run-mailcap is an effort to seamlessly support x/console/whatever use, but nmh (and sensible-tools) are messing things up, because they try to do part of the job themselfs. I think the easy way to fix this is to dump run-mailcap down so it doesn't interfere with what nmh is doing. > personally i think the NEWS.Debian that i added to 1.6-6 does spell out > the options sufficiently well, but i'm certainly open to suggestions > to make this more obvious. I think your explanation in the News.Debian is a good one. However since the differene between "run-mailcap --action=view" and "run-mailcap --action=cat" is somewhat subtle it took me a while to figure out, what's actually wrong. And I think the current default configuration probably works on many sytems - but only by chance, not by being right. If you think that this problem should be fixed in the mime-support or sensible-tools packages, then please reassign the bug there instead of closing it. HTE, Harald
