From mboxrd@z Thu Jan 1 00:00:00 1970 From: erik quanstrom Date: Sat, 9 Apr 2011 08:33:40 -0400 To: 9fans@9fans.net Message-ID: <198f66047c408afa6558d53bb9a755b2@ladd.quanstro.net> In-Reply-To: <86ei5behlx.fsf@cmarib.ramside> References: <86fwpz55nj.fsf@cmarib.ramside> <257867.782e4d7b.wsc0.mx@tumtum.plumbweb.net> <5ddd9deccbea5e8556dfc0c228b63311@ladd.quanstro.net> <86vcythf8h.fsf@cmarib.ramside> <86ipusd1wr.fsf@cmarib.ramside> <86zko3jt7n.fsf@cmarib.ramside> <86ei5behlx.fsf@cmarib.ramside> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Subject: Re: [9fans] Busy mouse WAS: Re: Making read(1) an rc(1) builtin? Topicbox-Message-UUID: ce4059e0-ead6-11e9-9d60-3106f5b1d025 > My load is also close to zero, when just moving the mouse. If, for > example, I do a "du -a" in an Acme "win" window, the mouse disappears > and/or becomes unusuably slow until Acme finishes. sounds like a video issue, rather than a mouse issue. i imagine that your machine is just slow. > Acme also hangs for me while retrieving files and directory listings on > /n/sources. Although the mouse remains responsive during that time, > Acme becomes unresponsive... not even selecting text with the button1 > works. that's how it works. acme's threading model means that everything comes to a screeching halt when you load a file. you just don't notice the delay when it's local. > > the mouse, the i would think that the fact that your machine > > is doing 8259-style interrupts has something to do with it. > > No hablo 8259. ?? http://en.wikipedia.org/wiki/Intel_8259 like the reptilian part of your brain, it proves that evolution is a bad housekeeper. - erik