From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Cc: ding@gnus.com
Subject: Re: C-d heuristics
Date: Fri, 26 Apr 2002 13:10:30 +0200 [thread overview]
Message-ID: <vaf4rhyn2ah.fsf@INBOX.tok.lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <ycc7kmva904.fsf@orff.wc.cray.com> (Ted Stern's message of "Thu, 25 Apr 2002 12:11:39 -0700")
Ted Stern <stern+gnus@cray.com> writes:
> It appears that if I forward the offending digest using
>
> C-u 4 M-x gnus-summary-mail-forward
>
> then you can still see the C-d problem exactly as I do. If I use
> the standard nil argument for C-c C-f forwarding, Gnus massages the
> message a bit before sending, and somehow manages to clear up the
> problem!
Actually, I think there is no problem. The MIME digest looks fine.
I guess the massaging comes because when MIME forwarding, Gnus parses
the MIME message into its structure, and when you send it again, Gnus
creates a new MIME structure.
That's why the MIME structure (in particular the part separators) are
different in the forwarded message.
Hm. I'm not sure what's involved in having C-d grok MIME digests
inside a normal forwarded message.
kai
--
Silence is foo!
next prev parent reply other threads:[~2002-04-26 11:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-25 19:11 Ted Stern
2002-04-26 11:10 ` Kai Großjohann [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-04-24 19:33 Ted Stern
2002-04-25 7:43 ` Kai Großjohann
2002-04-25 7:44 ` Kai Großjohann
2002-03-12 21:48 Dan Christensen
2002-03-12 22:08 ` Ted Stern
2002-04-24 3:02 ` Dan Christensen
2002-04-24 11:25 ` Kai Großjohann
2002-04-24 18:59 ` Dan Christensen
2002-04-24 19:36 ` 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=vaf4rhyn2ah.fsf@INBOX.tok.lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.de \
--cc=ding@gnus.com \
/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).