From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <7c3cee026a2ce088796be01f94aa45b9@mail.nanosouffle.net>
To: 9fans@9fans.net
From: Akshat Kumar <akumar@mail.nanosouffle.net>
Date: Fri, 27 Feb 2009 16:47:37 -0800
In-Reply-To: 31ec63c8fe239f38e1b5b53cf8215c8b@quanstro.net
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="upas-jarmyllzfyqaxldqmjkzwicgls"
Subject: Re: [9fans] rio Peculiarities
Topicbox-Message-UUID: aa1565f8-ead4-11e9-9d60-3106f5b1d025

This is a multi-part message in MIME format.
--upas-jarmyllzfyqaxldqmjkzwicgls
Content-Disposition: inline
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

I tried the pat patch just now, and it doesn't seem to improve the
load or change the other effect I mentioned.


ak

--upas-jarmyllzfyqaxldqmjkzwicgls
Content-Type: message/rfc822
Content-Disposition: inline

Delivered-To: akumar@mail.nanosouffle.net
Received: by 10.142.76.7 with SMTP id y7cs23366wfa;
        Fri, 27 Feb 2009 14:49:49 -0800 (PST)
Received: by 10.151.38.12 with SMTP id q12mr4820151ybj.68.1235774989273;
        Fri, 27 Feb 2009 14:49:49 -0800 (PST)
Return-Path: <9fans-bounces+akumar=mail.nanosouffle.net@9fans.net>
Received: from gouda.swtch.com (gouda.swtch.com [67.207.142.3])
        by mx.google.com with ESMTP id 11si24864096gxk.49.2009.02.27.14.49.48;
        Fri, 27 Feb 2009 14:49:49 -0800 (PST)
Received-SPF: pass (google.com: domain of 9fans-bounces+akumar=mail.nanosouffle.net@9fans.net designates 67.207.142.3 as permitted sender) client-ip=67.207.142.3;
Authentication-Results: mx.google.com; spf=pass (google.com: domain of 9fans-bounces+akumar=mail.nanosouffle.net@9fans.net designates 67.207.142.3 as permitted sender) smtp.mail=9fans-bounces+akumar=mail.nanosouffle.net@9fans.net
Received: from localhost ([127.0.0.1] helo=gouda.swtch.com)
	by gouda.swtch.com with esmtp (Exim 4.67)
	(envelope-from <9fans-bounces@9fans.net>)
	id 1LdBVb-0001qx-Gj; Fri, 27 Feb 2009 22:48:43 +0000
Received: from ladd.quanstro.net ([69.55.170.73])
	by gouda.swtch.com with esmtp (Exim 4.67)
	(envelope-from <quanstro@quanstro.net>) id 1LdBVZ-0001qs-NK
	for 9fans@9fans.net; Fri, 27 Feb 2009 22:48:41 +0000
Message-ID: <31ec63c8fe239f38e1b5b53cf8215c8b@quanstro.net>
From: erik quanstrom <quanstro@quanstro.net>
Date: Fri, 27 Feb 2009 17:48:40 -0500
To: 9fans@9fans.net
In-Reply-To: <6106b83c758fd550764970aba53bd530@mail.nanosouffle.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] rio Peculiarities
X-BeenThere: 9fans@9fans.net
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
List-Id: Fans of the OS Plan 9 from Bell Labs <9fans.9fans.net>
List-Unsubscribe: <http://mail.9fans.net/listinfo/9fans>,
	<mailto:9fans-request@9fans.net?subject=unsubscribe>
List-Archive: <http://mail.9fans.net/private/9fans>
List-Post: <mailto:9fans@9fans.net>
List-Help: <mailto:9fans-request@9fans.net?subject=help>
List-Subscribe: <http://mail.9fans.net/listinfo/9fans>,
	<mailto:9fans-request@9fans.net?subject=subscribe>
Sender: 9fans-bounces@9fans.net
Errors-To: 9fans-bounces+akumar=mail.nanosouffle.net@9fans.net

On Fri Feb 27 16:46:34 EST 2009, akumar@mail.nanosouffle.net wrote:
> Having a window which is `current' and `visible' but not on `top'
> gives rise to some effects of concern.  For example, scrolling this
> current window is cause for massive load on the system; if there are
> windows on top, making them current requires hiding the current one
> (clicking on them is ineffective).  My use for being in such a
> situation is, e.g., scrolling some acme body in the background while
> doing something with an rc window on the foreground (since my acme
> window takes up a large part of the screen).

take a look at the pat patch or the older mtrr patch.

- erik

--upas-jarmyllzfyqaxldqmjkzwicgls--