Re: gnus-summary-enter-digest-group

[Lars Magne Ingebrigtsen <larsi@gnus.org>]

Jack Vinson <jvinson@chevax.ecs.umass.edu> writes:

> 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

nndoc here displays a multipart message as a thread -- I find that
this models the structure of MIME messages in an enlightening manner.

And if you want to read a part, you just select it.

> 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.

I hadn't considered that, but I think that sounds way neat.  :-)

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen