Gnus development mailing list
 help / color / mirror / Atom feed
From: Stephen Berman <steve@ims.uni-stuttgart.de>
Subject: Re: multipart/alternative mail in doc group (bug?)
Date: Sun, 12 Oct 2003 12:19:50 +0200	[thread overview]
Message-ID: <m3ismu3ghl.fsf@feldmann.ruhr-uni-bochum.de> (raw)
In-Reply-To: <m3ad89u737.fsf@defun.localdomain>

On Fri, 10 Oct 2003 05:03:56 +0200 Jesper Harder <harder@myrealbox.com> wrote:

> Stephen Berman <steve@ims.uni-stuttgart.de> writes:
>
>> When I have several multipart/alternative mails saved in a Unix mail
>> file, make a doc group out of it with G f and then press <space>
>> [...]  This only happens if the first mail in the file is
>> multipart/alternative; if the first mail is not multipart but
>> e.g. just text/plain and all the following mails are
>> multipart/alternative, Gnus displays all entries correctly in the
>> summary buffer.
>
> Does it work if you do `C-u G f' and specify mbox as the type?

Yes it does; thanks!  I suppose the problem was that by not specifying
the type, Gnus guessed `mime-parts'?  Maybe I should have figured this
out, or just tried using the prefix argument, but it just didn't occur
to me that this was related to the problem.  I think it would be
helpful to note this possibility in the manual and perhaps also in the
docstring; maybe something like this: "If you want to create a doc
group of a specific type and the content-type of the mail could lead
Gnus to guess the wrong type (e.g., if you want to create an mbox
group but the (first) mail in the file has content-type
multipart/alternative), then be sure to use `C-u G f' to create the
group."

I still don't understand why Gnus only displayed the first of the
multipart messages; is this expected?

--Steve Berman




  reply	other threads:[~2003-10-12 10:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-04 13:29 Stephen Berman
2003-10-10  3:03 ` Jesper Harder
2003-10-12 10:19   ` Stephen Berman [this message]
2003-10-16 14:49     ` Lars Magne Ingebrigtsen

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=m3ismu3ghl.fsf@feldmann.ruhr-uni-bochum.de \
    --to=steve@ims.uni-stuttgart.de \
    /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).