From: vvv@vsu.ru
Subject: Re: bug in gnus-summary-enter-digest-group
Date: 15 Dec 2000 15:41:29 +0300 [thread overview]
Message-ID: <eyofydeu12.fsf@video.uic.vsu.ru> (raw)
In-Reply-To: <eyae9yezak.fsf@video.uic.vsu.ru>
"v" == vvv writes:
KG> Is it the `Topics' line that you were missing? As you can see, I
KG> get it. Or is something else missing here?
v> No, the original message was of type multipart/mixed and contained
v> the text part with the description of a bug, then a
v> multipart/digest part with the digest. the digest contains three
v> parts, -- topics, and two messages.
v> What you see when you press C-d is the contents of the digest:
v> topics and two messages. But where is the first text/plain part
v> with the description of the bug?
i'd like to add that perhaps i should have used M-C-d
(gnus-summary-read-document) instead of C-d
(gnus-summary-enter-digest-group). But neither of them shows the whole
MIME structure of the message.
Best,
v.
next prev parent reply other threads:[~2000-12-15 12:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-15 9:17 vvv
2000-12-15 10:37 ` Kai Großjohann
2000-12-15 10:47 ` vvv
2000-12-15 12:41 ` vvv [this message]
2000-12-15 13:00 ` Kai Großjohann
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=eyofydeu12.fsf@video.uic.vsu.ru \
--to=vvv@vsu.ru \
/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).