Gnus development mailing list
 help / color / mirror / Atom feed
From: wmperry@aventail.com (William M. Perry)
Cc: ding@gnus.org
Subject: Re: Shouldn't Gnus (er, W3) inline related images in <img src=cid:...>?
Date: 14 Aug 2000 09:00:29 -0500	[thread overview]
Message-ID: <86og2w2b9e.fsf@localhost.localdomain> (raw)
In-Reply-To: "Daniel Pittman"'s message of "14 Aug 2000 13:31:31 +1000"

"Daniel Pittman" <daniel@danann.net> writes:

> On 13 Aug 2000, Kai Großjohann <Kai.Grossjohann@CS.Uni-Dortmund.DE>
> wrote:
> 
> > On 11 Aug 2000, ShengHuo ZHU wrote:
> 
> [...]
> 
> > Is there a standard of some kind that we can turn to to find out what
> > is the right behavior?  Should the behavior of the metamail program be
> > considered a standard?
> 
> Last time I went hunting for information on this, that was the closest I
> got. 'metamail' seems to be the /only/ reference to how it 'should'
> work, and that's not actually documented.

RFC 1343 is where you should look - there are relevant chunks quoted from
it in the emacs/w3 manual.  It doesn't really seem to have anything to say
on dealing with multiple mailcap files.

We could assign a new weight by file location, and use that in
mm-viewer-lessp, but that could get tricky.

-Bill P.



  reply	other threads:[~2000-08-14 14:00 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
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 [this message]
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=86og2w2b9e.fsf@localhost.localdomain \
    --to=wmperry@aventail.com \
    --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).