From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <f06f77da91f42c6cf75074cbaefcaab2@mail.nanosouffle.net>
To: 9fans@9fans.net
From: Akshat Kumar <akumar@mail.nanosouffle.net>
Date: Fri, 27 Feb 2009 14:05:10 -0800
In-Reply-To: 79a364e5a34578cd32f858082fc93216@csplan9.rit.edu
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="upas-fyttverorstpodgrkcdbzjhpbm"
Subject: Re: [9fans] rio Peculiarities
Topicbox-Message-UUID: a9f33ed8-ead4-11e9-9d60-3106f5b1d025

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

echo current > /dev/wsys/%d/wctl


ak

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

Delivered-To: akumar@mail.nanosouffle.net
Received: by 10.142.76.7 with SMTP id y7cs22040wfa;
        Fri, 27 Feb 2009 13:52:38 -0800 (PST)
Received: by 10.224.20.82 with SMTP id e18mr4974217qab.46.1235771557301;
        Fri, 27 Feb 2009 13:52:37 -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 38si1981337qyk.124.2009.02.27.13.52.36;
        Fri, 27 Feb 2009 13:52:37 -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 1LdAcP-0001Gz-QR; Fri, 27 Feb 2009 21:51:42 +0000
Received: from csplan9.rit.edu
	([129.21.34.236] helo=csplan9.rit.edu. ident=none)
	by gouda.swtch.com with esmtp (Exim 4.67)
	(envelope-from <john@csplan9.rit.edu>) id 1LdAcL-0001Gs-5n
	for 9fans@9fans.net; Fri, 27 Feb 2009 21:51:37 +0000
Message-ID: <79a364e5a34578cd32f858082fc93216@csplan9.rit.edu>
To: 9fans@9fans.net
Date: Fri, 27 Feb 2009 16:51:34 -0500
From: john@csplan9.rit.edu
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

> 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).
>
>
> Not particularly important, but an interesting case nonetheless,
> ak

How exactly are you making a window current without bringing it to the
top?


John


--upas-fyttverorstpodgrkcdbzjhpbm--