Re: Better handling of reply configuration

[Reid Rivenburgh <reid@lanl.gov>]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=us-ascii, Size: 1520 bytes --]

 >> Kai Großjohann writes:

 > Reid Rivenburgh <reid@lanl.gov> writes:
 >> The problem is that when replying, the reply buffer takes over the
 >> frame.

 > Not true for me.  I haven't changed the default settings concerning
 > windows.

 > When I hit `R' or `F', the original article buffer disappears and
 > the reply buffer takes the whole frame.  This is okay, since the
 > original article is quoted in the reply and can therefore be seen.

 > When I hit `r' or `f', the frame is split, showing both the
 > original article and the reply.

 > Did you change the frame/window configuration?

I think you're right, I was confused about that.  (I've been playing
with so many configurations here that I'm getting loopy.)  The
original article displayed with `r' or `f' is a raw copy, correct?
With no highlighting and all headers displayed.  Usually, the headers
fill up the entire window, unfortunately....  It'd be nice if it
automatically scrolled to the end.  (Is there a hook for that?  I
haven't bothered looking, just wondering.)

In any case, the problem still stands that if I want to refer to a
different message in the same or a different group, it's a bit awkward
to navigate.  I think the configuration I was trying to achieve would
help there.  It would also just display the normal article buffer
(along with the summary buffer) rather than the raw copy, which is
better in most cases, I think.

Thanks for straightening me out regarding the above, though.

Reid