view message/rfc822 in separate buffer?

view message/rfc822 in separate buffer?

[Kai Großjohann]

Once upon a time, I could click on a message/rfc822 part and it was
displayed in its own buffer.  I could then hit `r' to reply to that
message.

At least I think this used to be possible...

How do I do that now, given that message/rfc822 parts are displayed
inline?

kai
-- 
Beware of flying birch trees.

Re: view message/rfc822 in separate buffer?

[Steinar Bang]

>>>>> Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann):

> Once upon a time, I could click on a message/rfc822 part and it was
> displayed in its own buffer.  I could then hit `r' to reply to that
> message.

> At least I think this used to be possible...

> How do I do that now, given that message/rfc822 parts are displayed
> inline?

	C-d
then walk the cursor down to the correct part, press SPC, followed by
r. 

Re: view message/rfc822 in separate buffer?

[Toby Speight]

Kai> Kai Großjohann <URL:mailto:Kai.Grossjohann@CS.Uni-Dortmund.DE>

0> In article <200005041530.RAA04817@lucy.cs.uni-dortmund.de>, Kai
0> wrote:

Kai> Once upon a time, I could click on a message/rfc822 part and it
Kai> was displayed in its own buffer.  I could then hit `r' to reply
Kai> to that message.
Kai>
Kai> How do I do that now, given that message/rfc822 parts are displayed
Kai> inline?

Is C-d good enough for that?

Re: view message/rfc822 in separate buffer?

[Kai Großjohann]

Why didn't I think of `C-d'?  Of course that will work.  Hm.

But the old behavior was quite convenient, too, and I think I recall
that Lars has said he wants to provide all functionality with the
normal MIME display, without relying on C-d.  So...

Lars?

kai
-- 
Beware of flying birch trees.

Re: view message/rfc822 in separate buffer?

[Lars Magne Ingebrigtsen]

Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:

> Why didn't I think of `C-d'?  Of course that will work.  Hm.
> 
> But the old behavior was quite convenient, too, and I think I recall
> that Lars has said he wants to provide all functionality with the
> normal MIME display, without relying on C-d.  So...

You can get the old behavior by writing and specifying a different
viewer for message/rfc822.  I think the current behavior is really
nice, though.

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

Re: view message/rfc822 in separate buffer?

[Karl Kleinpaste]

Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:
> How do I do that now, given that message/rfc822 parts are displayed
> inline?

Perhaps tear the message apart with `C-d', then reply to the
component pieces?

Re: view message/rfc822 in separate buffer?

[Kai Großjohann]

Karl Kleinpaste <karl@charcoal.com> writes:

> Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:
> > How do I do that now, given that message/rfc822 parts are displayed
> > inline?
> 
> Perhaps tear the message apart with `C-d', then reply to the
> component pieces?

In this particular case, C-d cannot find any articles within the
digest.  Hmm...  Here's what the message looks like:

    From: Stefan Kokkelink <skokkeli@mathematik.Uni-Osnabrueck.DE>
    To: kai.grossjohann@cs.uni-dortmund.de
    Subject: [autarch@urth.org: XML::XPath & XSLT]
    Mime-Version: 1.0
    Content-Type: text/plain; charset=us-ascii
    X-Mailer: Mutt 1.0i

    ----- Forwarded message from Autarch <autarch@urth.org> -----

    Date: Mon, 1 May 2000 23:32:22 -0500 (CDT)
    From: Autarch <autarch@urth.org>
    To: "Perl-XML Mailing List" <perl-xml@listserv.activestate.com>
    Subject: XML::XPath & XSLT

    [...]

    ----- End forwarded message -----

I have deleted lots of header lines, too.

I now see that this kind of forward (apparently produced by mutt) is
not in nndoc-type-alist.

kai
-- 
Beware of flying birch trees.

Re: view message/rfc822 in separate buffer?

[Shenghuo ZHU]

>>>>> "KG" == Kai Großjohann <Kai.Grossjohann@CS.Uni-Dortmund.DE> writes:

KG> I now see that this kind of forward (apparently produced by mutt) is
KG> not in nndoc-type-alist.

Fixed.  Now, the forward regexps in nndoc.el and mm-uu.el are the
same.

-- 
Shenghuo

Re: view message/rfc822 in separate buffer?

[Karl Eichwalder]

Shenghuo ZHU <zsh@cs.rochester.edu> writes:

> Fixed.  Now, the forward regexps in nndoc.el and mm-uu.el are the
> same.

Thanks.  C-d (`gnus-summary-enter-digest-group') and  then r
(`gnus-summary-reply') works good, but f (`gnus-summary-followup') does
not do what I expect:

`gnus-summary-followup' put the receiver (To) of the message plus the
receiver of the message/rfc822 part into the To of the reply.  For my
understanding it should leave alone the To of the main message but make
use of To and Cc of the message/rfc822 part.

Do you understand what I mean.  If it's unclear, I can provide a sketch.

-- 
work : ke@suse.de                          |
     : http://www.suse.de/~ke/             |          ------    ,__o
home : ke@gnu.franken.de                   |         ------   _-\_<,
     : http://www.franken.de/users/gnu/ke/ |        ------   (*)/'(*)

Re: view message/rfc822 in separate buffer?

[Shenghuo ZHU]

>>>>> "Karl" == Karl Eichwalder <ke@gnu.franken.de> writes:

Karl> Thanks.  C-d (`gnus-summary-enter-digest-group') and  then r
Karl> (`gnus-summary-reply') works good, but f (`gnus-summary-followup') does
Karl> not do what I expect:

Karl> `gnus-summary-followup' put the receiver (To) of the message plus the
Karl> receiver of the message/rfc822 part into the To of the reply.  For my
Karl> understanding it should leave alone the To of the main message but make
Karl> use of To and Cc of the message/rfc822 part.

Karl> Do you understand what I mean.  If it's unclear, I can provide a sketch.

The mail address of the main message is intentionally added.  A
comment reads "have the digest group inherit the main mail address of
the parent article."

-- 
Shenghuo

Re: view message/rfc822 in separate buffer?

[Karl Eichwalder]

Shenghuo ZHU <zsh@cs.rochester.edu> writes:

> The mail address of the main message is intentionally added.  A
> comment reads "have the digest group inherit the main mail address of
> the parent article."

Okay, it could be useful.  But why not add the To address of the part,
too?

-- 
work : ke@suse.de                          |
     : http://www.suse.de/~ke/             |          ------    ,__o
home : ke@gnu.franken.de                   |         ------   _-\_<,
     : http://www.franken.de/users/gnu/ke/ |        ------   (*)/'(*)

Re: view message/rfc822 in separate buffer?

[Shenghuo ZHU]

>>>>> "Karl" == Karl Eichwalder <ke@gnu.franken.de> writes:

Karl> Shenghuo ZHU <zsh@cs.rochester.edu> writes:
>> The mail address of the main message is intentionally added.  A
>> comment reads "have the digest group inherit the main mail address of
>> the parent article."

Karl> Okay, it could be useful.  But why not add the To address of the
Karl> part, too?

The main mail address is added as to-address of the group parameter.
It might be the reason why the behavior of followup changes. You can
try wide-reply `S w'.

-- 
Shenghuo

Re: view message/rfc822 in separate buffer?

[Karl Eichwalder]

Shenghuo ZHU <zsh@cs.rochester.edu> writes:

> The main mail address is added as to-address of the group parameter.
> It might be the reason why the behavior of followup changes. You can
> try wide-reply `S w'.

Thanks for enlightenment.  This works somehow, but it "forgets" to add
the main mail address.  At point point  I admit I'm not completely sure
what't the right thing to ask for :)

-- 
work : ke@suse.de                          |
     : http://www.suse.de/~ke/             |          ------    ,__o
home : ke@gnu.franken.de                   |         ------   _-\_<,
     : http://www.franken.de/users/gnu/ke/ |        ------   (*)/'(*)