> At the moment ~/.mailcap takes precedence over /etc/mailcap, so a user >>>> can't specify a program to use for types that don't have a rule in >>>> /etc/mailcap. >>>> >>>> Specifically, I'd like to be able to specify fallbacks for text/* and >>>> application/* (and just point them to my editor). If I do this at the >>>> moment, then of course the setting overrides everything in >>>> /etc/mailcap, which isn't what I want. >>>> >>> >>> I think that what you're asking would go against the directions of the >>> RFCs. >>> >>> Even if I change the behavion of run-mailcap, though, it may not help you >>> as many programs implement the processing of ~/.mailcap and /etc/mailcap in >>> their own code rather than calling my program. Thus, the operation of the >>> system would not be consistent as it would vary depending on what program >>> you're running. >>> >> >> OK. Is what I want to do stupid? If not, how do you think it is best >> accomplished? >> > > Not at all. I understand why that would be beneficial. However, the "/*" > entries are more of an afterthought in mime-types rather than a planned out > feature. > > If you don't care about per-user, you could just add a rule is the > /usr/share/lib/mime/packages (or something like that) with the rule you > want. That will make it system-wide next time update-mime is run. >
With the release of mime-support I'm about to make, you can do "update-mime --local" to generate a ~/.mailcap entry that will completely replace the one in /etc. I think that with a ~/.mailcap.order and some custom rules inserted in the correct place, you can achieve what you want. Brian [email protected] ----------------------------------------------------------------------------------------- Treat someone as they are and they will remain that way. Treat someone as they can be and they will become that way.
