[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Nmh-workers] Default setup broken on Debian?
From: |
Alexander Zangerl |
Subject: |
Re: [Nmh-workers] Default setup broken on Debian? |
Date: |
Tue, 03 Mar 2015 18:41:32 +1000 |
On Mon, 02 Mar 2015 17:51:22 +0000, Conrad Hughes writes:
>Debian's version sends
> everything (although sometimes there's no-such-file, causing
> failures) to GUI helper applications, which feels like something of
> a regression vs 1.5 behaviour.
debian's exmh uses run-mailcap, which is the only thing we can depend on
to be available. after all not everybody has (or wants) lynx installed,
or libreoffice or <insert mime handler of your personal choice
which everybody else hates>.
i'd say the clean debianish solution for delegating mime types to
specific apps would be to configure /etc/mailcap and/or /etc/mailcap.order,
so that the run-mailcap mime handler learns of your preferences.
the nmh way would be to prime your mh_profile with your personal
mhshow-mimetype/subtype entries for mhshow, and/or massaging /etc/mhn.defaults.
the only difference between upstream's mhn.defaults and the one shipped with
debian's nmh are the 4+6 lines for mime types
application/postscript, /msword, /pdf, image/* (upstream and too specific)
vs the generic application/*, audio/*, image/*, video/*, message/* and
text/* (debian).
i guess i might add a specific entry for text/plain to make show
"fall back" to the default %l+moreproc, to divert/refine the
generic text/* entry (which we need for text/richtext).
regards
az
--
Alexander Zangerl + GPG Key 0xB963BD5F (or 0x42BD645D) + http://snafu.priv.at/
Buchen sollst du suchen, Bei den Eiben kannst du speiben. -- Gunkl
signature.asc
Description: Digital Signature
Re: [Nmh-workers] Default setup broken on Debian?,
Alexander Zangerl <=