[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
LYNX-DEV Re: strange mailcap problem
From: |
Klaus Weide |
Subject: |
LYNX-DEV Re: strange mailcap problem |
Date: |
Tue, 13 May 1997 12:20:35 -0500 (CDT) |
On Tue, 13 May 1997, Larry W. Virden, x2487 wrote:
> an interesting phenom. For some reason, additional entries, not from
> my mailcap, are being added to the mix - an entry or two for
> application/postscript, an entry for image/*, one for image/gif,
> TWO entries for image/jpeg, an entry for message/external-body, and one
> for x-conference/x-cooltalk.
Read the comments in lynx.cfg for XLOADIMAGE_COMMAND, VIEWER,
GLOBAL_MAILCAP, and PERSONAL_MAILCAP. They mention all the places where
viewers can come from.
By the way, the following descriprion for *_MAILCAP is slightly incorrect,
# The global and personal MAILCAP files allow you to specify external
# viewers to be spawned when Lynx encounters different MIME types, which
# will override any of the suffix maps in this (lynx.cfg) configuration
^^^^^^^^^^^
# file, or in src/HTInit.c. See RFC-MAILCAP.txt in the docs subdirectory
# and the example mailcap file in the samples subdirectory.
That should be "viewers".
> Is there a flag I can give lynx to tell it to show me where it's getting
> these from?
lynx -trace shows the ones from mailcap files at the beginning, but not
others. If you don't see it there and it's not hardwired in HTInit.c
(and x-conference/x-cooltalk certainly isn't, unless you have changed
the source), it must be from your lynx.cfg.
Klaus
;
; To UNSUBSCRIBE: Send a mail message to address@hidden
; with "unsubscribe lynx-dev" (without the
; quotation marks) on a line by itself.
;
- LYNX-DEV Re: strange mailcap problem,
Klaus Weide <=