MIME forwards

MIME forwards

[Per Abrahamsen]

I don't care about the format, but I'd like to _see_ the message being
forwarded.  I mostly use forward for spam complaints, and seeing the
headers are important then.

Maybe the *Article* buffer should be shown in the other window, like
when you reply or followup?

Re: MIME forwards

[Lars Magne Ingebrigtsen]

Per Abrahamsen <abraham@dina.kvl.dk> writes:

> I don't care about the format, but I'd like to _see_ the message being
> forwarded.  I mostly use forward for spam complaints, and seeing the
> headers are important then.
> 
> Maybe the *Article* buffer should be shown in the other window, like
> when you reply or followup?

No, I think message/rfc822 parts should be displayed inline in the
article buffer.  Even though that means having to `C-u g' to see the
complete headers of the message/rfc822 parts.  And now that I've
calmed down a bit, I think I'll write it today.

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

Re: MIME forwards

[Per Abrahamsen]

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> Per Abrahamsen <abraham@dina.kvl.dk> writes:
> 
> > I don't care about the format, but I'd like to _see_ the message being
> > forwarded.  I mostly use forward for spam complaints, and seeing the
> > headers are important then.
> > 
> > Maybe the *Article* buffer should be shown in the other window, like
> > when you reply or followup?
> 
> No, I think message/rfc822 parts should be displayed inline in the
> article buffer.  

Atually, I was talking about the message buffer.  I.e. when *I* am the
one doing the forwarding, not when I'm reading it.

Re: MIME forwards

[Hrvoje Niksic]

Per Abrahamsen <abraham@dina.kvl.dk> writes:

> I don't care about the format, but I'd like to _see_ the message
> being forwarded.

I agree with this.  Instead of using a separate buffer, the message
buffer should be setup like this:

    --text follows this line--
    <-- point here

    <#part blah blah blah...>
    ... full message text here...
    <#/part>

That is probably a better idea than having a separate buffer because
it allows you to edit things out without switching buffer.

Re: MIME forwards

[Lars Magne Ingebrigtsen]

Hrvoje Niksic <hniksic@srce.hr> writes:

> I agree with this.  Instead of using a separate buffer, the message
> buffer should be setup like this:
> 
>     --text follows this line--
>     <-- point here
> 
>     <#part blah blah blah...>
>     ... full message text here...
>     <#/!part>

Uhm; yes.  Fix in Pterodactyl Gnus v0.78.

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