On Thu, May 15, 2003 at 02:13:32PM +0200, mcINEK wrote: > > > It won't work, because the aren't any 'standards'. I don't have idea how > > > make x/non-x choice from mailcap. I REALLY think alternatives could be > > > good. > > > > It's done in there, all over the place! There's a 'test' option, which > > is meant to use a line conditionally; it's commonly used to test whether > > $DISPLAY is set, which is *exactly* what you need. > > No, it doesn't. There can be more tjan one line describing the same mime > type. And what then?
The first one will be used. > Solving this problem will be sorting content of > /usr/lib/mime/packages by appropiate types, such as: > > /usr/lib/mime/packages/text-html/mozilla, > content (example): x,/usr/bin/mozilla > /usr/lib/mime/packages/text-html/links > content: text,/usr/bin/mozilla > > And on that base update-mime can generate /etc/mailcap. Of course if > they'd be more browsers it only can choose one, but in the present time > it's the same. You don't need to do that. Leave /etc/mailcap the way it is; system-wide preferences wrt default applications suck anyway :-) > If there'd be a types tree like that making front-end will make sense, > otherwise no. User'd choose a program from that directory structure. Uh. You can create such a tree in-memory, no? Parsing the file is not *that* hard. -- Debian GNU/Linux -- http://www.debian.org Nederlandstalige Linux-documentatie -- http://nl.linux.org "An expert can usually spot the difference between a fake charge and a full one, but there are plenty of dead experts." -- National Geographic Channel, in a documentary about large African beasts.
pgpcIpVqYnnIK.pgp
Description: PGP signature
