From: Micah Stetson <micah@cnm-vra.com>
To: 9fans@cse.psu.edu
Subject: [9fans] rio and acme scrolling
Date: Fri, 26 Mar 2004 16:58:28 -0800 [thread overview]
Message-ID: <20040327005828.GA2896@epaphras.cnm-vra.com> (raw)
Lately, I've been having a problem with scrolling under
acme and rio. Basically, unless I am VERY quick with my
click on the scroll bar, the window scrolls much more
than a single click should. The delay that used to occur
between the initial one-click scroll and the hold-the-button
continuous scrolling is no longer there. However, I
don't see any recent changes (looking in sources' dump)
that look to me like they would affect that.
Also, the symptoms are kind of weird. When I boot my
laptop off of my newly assembled (yay) Fossil/Venti/Auth
server, which is up to date as of today, I get the effect
consistently. I think I remember seeing it happen booting
from the hard disk on my laptop a few weeks ago, but I
can't be sure. Still, I booted on my laptop this afternoon
and couldn't reproduce the problem. Even when I would
cpu to the new server and run the rio or acme binary from
there, it didn't happen. So I updated the laptop from
sources (it hadn't been since late February) and continued
to puzzle about it. I did not reboot, and unsurprisingly,
the behavior didn't change. But after the update, I left
the machine sitting for an hour or two while I worked on
other things. When I came back, I got the weird scrolling.
But I still haven't rebooted. Now this puzzles me more
than everything else put together. What happened while
I wasn't looking?
Thanks,
Micah
next reply other threads:[~2004-03-27 0:58 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-27 0:58 Micah Stetson [this message]
2004-03-27 1:51 ` Russ Cox
2004-03-27 5:07 ` Micah Stetson
2004-03-27 15:01 ` David Presotto
2004-03-27 15:07 ` Sape Mullender
2004-03-27 15:12 ` David Presotto
2004-03-27 20:58 ` Derek Fawcus
2004-03-27 15:22 ` Richard Miller
2004-03-27 15:36 ` Sape Mullender
2004-03-27 15:38 ` David Presotto
2004-03-27 15:38 ` Russ Cox
2004-03-27 17:03 ` Richard Miller
2004-03-27 16:07 ` andrey mirtchovski
2004-03-27 20:11 ` Micah Stetson
2004-03-27 20:45 ` thinkpads (was Re: [9fans] rio and acme scrolling) Axel Belinfante
2004-03-28 11:07 ` [9fans] rio and acme scrolling matt
2004-03-29 15:18 ` splite
2004-03-27 20:27 ` Micah Stetson
2004-03-27 23:57 ` Micah Stetson
2004-03-27 3:14 ` jmk
2004-03-27 10:21 ` a
2004-03-27 10:50 ` Dave Lukes
2004-03-29 13:41 ` blstuart
2004-03-29 14:33 ` Russ Cox
2004-03-29 14:36 ` matt
2004-03-29 15:57 ` Axel Belinfante
2004-03-29 17:31 ` Axel Belinfante
2004-03-29 18:42 ` [9fans] hget rog
2004-03-29 19:50 ` Russ Cox
2004-03-29 20:12 ` rog
2004-03-29 20:16 ` Russ Cox
2004-03-29 20:40 ` rog
2004-03-29 20:42 ` Russ Cox
2004-03-29 21:12 ` rog
2004-03-29 22:23 ` Charles Forsyth
2004-03-29 21:36 ` rog
2004-03-29 23:39 ` Charles Forsyth
2004-03-29 22:48 ` rog
2004-03-29 21:46 ` boyd, rounin
2004-03-29 23:01 ` rog
2004-03-29 22:17 ` boyd, rounin
2004-03-29 23:34 ` rog
2004-03-29 22:49 ` boyd, rounin
2004-03-30 10:19 ` Steve Simon
2004-03-30 0:02 ` Charles Forsyth
2004-03-29 23:22 ` rog
2004-03-29 19:58 ` David Tolpin
2004-03-29 20:08 ` David Tolpin
2004-03-29 20:18 ` rog
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=20040327005828.GA2896@epaphras.cnm-vra.com \
--to=micah@cnm-vra.com \
--cc=9fans@cse.psu.edu \
/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).