[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: lynx-dev .mailcap vs. HTSetPresentation
From: |
Thomas Dickey |
Subject: |
Re: lynx-dev .mailcap vs. HTSetPresentation |
Date: |
Wed, 28 Jan 2004 17:29:40 -0500 (EST) |
On Wed, 28 Jan 2004, Doug Kaufman wrote:
> On Wed, 28 Jan 2004 address@hidden wrote:
>
> > I recently decided I could view MPEGs, etc. with a shell command on
> > my iBook. So I put the command in my ~/.mailcap and pointed Lynx at
> > a video/mpeg. Nothing happened. I did a trace. I found Lynx was
> > calling something called "mpeg_play", which doesn't exist. As a
> > circumvention, I put a one-line script in my PATH. But I disagree
> > with Lynx here.
> > ...
> > o Perhaps the hard-coded "mpeg_play" can be overridden in lynx.cfg. But
> > this shouldn't be necessary. .mailcap is the central place where I
> > should be able to define all helper apps, putting only desired
> > exceptions in lynx.cfg. Mailcap is specified in RFC 1524; Lynx should
> > respect that.
>
> As far as I know lynx DOES follow the values in .mailcap, overriding
> anything specified in lynx.cfg. I thought the order was HTInit.c
> defaults, then the VIEWER commands in lynx.cfg, then the global
> mailcap, then your personal .mailcap.
sounds right. But seeing the effect of the settings can be hard.
It would be nice to add something to the "=" screen that shows the
type that's derived (and which level it comes from).
--
Thomas E. Dickey
http://invisible-island.net
ftp://invisible-island.net
; To UNSUBSCRIBE: Send "unsubscribe lynx-dev" to address@hidden