From: Akshat Kumar <akumar@mail.nanosouffle.net>
To: 9fans@9fans.net
Subject: Re: [9fans] rio Peculiarities
Date: Fri, 27 Feb 2009 16:47:37 -0800 [thread overview]
Message-ID: <7c3cee026a2ce088796be01f94aa45b9@mail.nanosouffle.net> (raw)
In-Reply-To: 31ec63c8fe239f38e1b5b53cf8215c8b@quanstro.net
[-- Attachment #1: Type: text/plain, Size: 122 bytes --]
I tried the pat patch just now, and it doesn't seem to improve the
load or change the other effect I mentioned.
ak
[-- Attachment #2: Type: message/rfc822, Size: 3061 bytes --]
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] rio Peculiarities
Date: Fri, 27 Feb 2009 17:48:40 -0500
Message-ID: <31ec63c8fe239f38e1b5b53cf8215c8b@quanstro.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
next reply other threads:[~2009-02-28 0:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-28 0:47 Akshat Kumar [this message]
2009-02-28 2:26 ` erik quanstrom
-- strict thread matches above, loose matches on Subject: below --
2009-02-27 22:05 Akshat Kumar
2009-02-27 21:44 Akshat Kumar
2009-02-27 21:51 ` john
2009-02-27 22:48 ` erik quanstrom
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7c3cee026a2ce088796be01f94aa45b9@mail.nanosouffle.net \
--to=akumar@mail.nanosouffle.net \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).