Re: fdisp window not scrolling (bug?)

Two things:

1: The fdisp.tcl fixed got picked up for 2.7.2

2: what mailer setup is causing this horribly
nested message structure for simple text messages?
Content-Type: multipart/mixed;
        boundary="----_=_NextPart_000_01C4F439.BBD26EA0"
Content-Type: text/plain;
Content-Type: message/rfc822
Content-Type: multipart/mixed;
        boundary="----_=_NextPart_002_01C4F439.BBD26EA0"
Content-Type: text/plain
Content-Type: text/plain;

>>>[email protected] said:
 [some stuff omitted]
 > ------_=_NextPart_000_01C4F439.BBD26EA0
 > Content-Type: message/rfc822
 > 
 > Subject: 
 > Date: Thu, 6 Jan 2005 13:50:57 -0800 
 > MIME-Version: 1.0
 > Content-Type: multipart/mixed;
 > 	boundary="----_=_NextPart_002_01C4F439.BBD26EA0"
 > 
 > 
 > ------_=_NextPart_002_01C4F439.BBD26EA0
 > Content-Type: text/plain
 > 
 > 
 > 
 > ------_=_NextPart_002_01C4F439.BBD26EA0
 > Content-Type: text/plain;
 > 	name="ATT74455.txt"
 > Content-Disposition: attachment;
 > 	filename="ATT74455.txt"
 > 
 > On Thu, 06 Jan 2005 22:12:21 +0100, [email protected] said:
 > > 
 > > I've recently installed the "zaxismapping 4 5" xsetting to get the
 > > wheel on the mouse to do the right thing. I noticed that the message
 > > and ftoc displays slaves up to the wheel for scrolling, but the fdisp
 > > (the uppermost panel) does not. Is that intentional? This is on 2.7.0
 > > (gentoo/Linux version). 
 > 
 > No, it was a missing call to 'mscroll', I've added it to the CVS tree..
 > 
 > 
 > ------_=_NextPart_002_01C4F439.BBD26EA0--
 > 
 > ------_=_NextPart_000_01C4F439.BBD26EA0--
 > 

--
Brent Welch
Software Architect, Panasas Inc
Delivering the premier storage system for scalable Linux clusters

www.panasas.com
[email protected]