Gnus development mailing list
 help / color / mirror / Atom feed
From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Cc: ding@gnus.org
Subject: Re: Shouldn't Gnus (er, W3) inline related images in <img src=cid:...>?
Date: 11 Aug 2000 15:17:50 +0200	[thread overview]
Message-ID: <vafya24ndhd.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: ShengHuo ZHU's message of "11 Aug 2000 00:33:35 -0400"

On 11 Aug 2000, ShengHuo ZHU wrote:

> Check your mailcap files.  The image/jpeg entry should look like
> 
>     image/jpeg; xv %s
> 
> instead of
> 
>     image/jpeg; xv '%s'

My Debian potato installation contains /etc/mailcap with:

    image/jpeg; xv '%s'

My home dir contains ~/.mailcap with:

    image/*; xv %s

The value of mailcap-mime-data contains the ~/.mailcap entry first,
and the /etc/mailcap entry after that.

When viewing a JPEG file, Gnus uses the /etc/mailcap entry.

Hm.

How are /etc/mailcap and ~/.mailcap supposed to interact?  OT1H,
~/.mailcap should override /etc/mailcap, but OTOH, more specific
settings should override more general settings.

But somehow, this feels wrong.  After all, I told it to use xv for all
kinds of images in my ~/.mailrc -- why should I have to specify each
image type separately?

Or maybe Gnus does use the first matching entry it finds, but searches
from the end of the list, rather than from the beginning?

kai
-- 
I like BOTH kinds of music.



  reply	other threads:[~2000-08-11 13:17 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-02-29 21:40 Karl Kleinpaste
2000-03-05 14:24 ` William M. Perry
2000-03-05 14:35   ` Karl Kleinpaste
2000-04-20 20:26 ` Lars Magne Ingebrigtsen
2000-04-20 22:02   ` Michael Harnois
2000-04-20 22:53     ` Lars Magne Ingebrigtsen
2000-04-21 22:37       ` Michael Harnois
2000-04-22 12:14         ` Lars Magne Ingebrigtsen
2000-04-23 16:46           ` Michael Harnois
2000-08-10 18:48             ` Lars Magne Ingebrigtsen
2000-08-10 18:53               ` Roland Mas
2000-08-10 19:00                 ` Lars Magne Ingebrigtsen
2000-08-10 19:02                   ` Lars Magne Ingebrigtsen
2000-08-11  2:04                   ` Rene H. Larsen
2000-08-11  4:33                     ` ShengHuo ZHU
2000-08-11 13:17                       ` Kai Großjohann [this message]
2000-08-11 13:48                         ` ShengHuo ZHU
2000-08-11 21:03                           ` Kai Großjohann
2000-08-11 21:41                             ` ShengHuo ZHU
2000-08-13 16:07                               ` Kai Großjohann
2000-08-14  3:31                                 ` Daniel Pittman
2000-08-14 14:00                                   ` William M. Perry
2000-08-11 23:51                       ` Rene H. Larsen
2000-08-12  1:04                         ` Rene H. Larsen
2000-08-14 12:04                           ` `mm-quote-arg' and shell quoting in mailcap (was: Shouldn't...) Toby Speight
2000-08-15  0:35                             ` Rene H. Larsen
2000-08-15 12:51                               ` `mm-quote-arg' and shell quoting in mailcap Toby Speight
2000-12-04  1:46                               ` `mm-quote-arg' and shell quoting in mailcap (was: Shouldn't...) Greg Stark
2000-08-15 13:09                           ` Shouldn't Gnus (er, W3) inline related images in <img src=cid:...>? François Pinard

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=vafya24ndhd.fsf@lucy.cs.uni-dortmund.de \
    --to=kai.grossjohann@cs.uni-dortmund.de \
    --cc=ding@gnus.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).