From: Jack Vinson <jvinson@chevax.ecs.umass.edu>
Subject: gnus-summary-enter-digest-group
Date: 15 Feb 1999 14:09:21 -0600 [thread overview]
Message-ID: <wkbtivpgy6.fsf@chevax.ecs.umass.edu> (raw)
When I use gnus-summary-enter-digest-group on a forwarded message, I get
something different than what I expect to get. For example, a message from
a friend has 1) a text part and 2) the forward. When I Ctrl-D on the
message, it is displayed as follows (after unhiding the thread):
[ 103: *Marci Cohen ] <* mixed> Fwd: this is the message
[ 2: *Marci Cohen ] <1 text>
[ 88: *Marci Cohen ] <2 rfc822>
[ 67: *Moshe ] <2 text> this is the message
What I would expect is something like
[ 2: *Marci Cohen ] <1 text>
[ 67: *Moshe ] <2 text> this is the message
which represents the text from Marci and the original message from Moshe.
I understand that the gnus-summary-enter-digest-group function has to deal
with all sorts of messages. Could this be done better? What ends up
happening is that I can keep hitting running
gnus-summary-enter-digest-group on the subsequent message and get
infinitely nesting *Summary* buffers that all look the same.
This is in pgnus 0.72, although I am fairly sure I saw it in 0.75.
--
Jack Vinson <jvinson@chevax.ecs.umass.edu> http://www.cis.upenn.edu/~vinson/
Zippy: TAILFINS!! ...click...
next reply other threads:[~1999-02-15 20:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-02-15 20:09 Jack Vinson [this message]
1999-02-19 16:10 ` gnus-summary-enter-digest-group Lars Magne Ingebrigtsen
1999-02-19 18:39 ` gnus-summary-enter-digest-group Kai.Grossjohann
1999-02-19 21:36 ` gnus-summary-enter-digest-group Lars Magne Ingebrigtsen
1999-02-20 12:03 ` gnus-summary-enter-digest-group Per Abrahamsen
1999-02-21 12:36 ` gnus-summary-enter-digest-group Kai.Grossjohann
1999-02-26 6:52 ` gnus-summary-enter-digest-group Lars Magne Ingebrigtsen
1999-02-26 15:37 ` gnus-summary-enter-digest-group Kai.Grossjohann
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=wkbtivpgy6.fsf@chevax.ecs.umass.edu \
--to=jvinson@chevax.ecs.umass.edu \
/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).