From: Lucio De Re <lucio@proxima.alt.za>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] weird cursor motion
Date: Thu, 26 Apr 2001 06:11:25 +0200 [thread overview]
Message-ID: <20010426061124.A354@cackle.proxima.alt.za> (raw)
In-Reply-To: <LPBBIBIIHKHEGDBPHBDOMEFNCAAA.kiwane@dream.com>; from kazumi iwane on Thu, Apr 26, 2001 at 12:26:59AM +0900
On Thu, Apr 26, 2001 at 12:26:59AM +0900, kazumi iwane wrote:
>
> When acme automatically moves the cursor around, like when
> searching for a piece of text or resizing a window, often times
> (but not always) the cursor symbol on the screen stays where
> it was, until I wiggle the mouse a little bit, then it immedately
> jumps to where it is supposed to be. As if the cursor was
> daydreaming... Has anyone seen this?
>
On that subject, if somewhat tangential: vncviewer is terribly
irritating (no matter what platform, I should imagine) when using
"wily". The cursor motion is entirely defeated by the viewer's cursor
position :-(
Just an amusing discovery. There had to be some place where
vncviewer wasn't going to work properly.
And on a related note, I had at least one instance where I would have
given my right hand for a second mouse, while using acme. Well, not
that a second mouse would have been terribly useful to a one-handed
person, but you get my drift...
MS Windows (I've tried '95, '98 and NT) responds quite well to two of
the rodents (yes, I have no idea if they are mice or mouses, like
mongoose) but with only one cursor. I should imagine that grafting a
second mouse channel on Plan 9 would be easier (at the filesystem
level, coercing the software to use it would be a different
challenge).
++L
next prev parent reply other threads:[~2001-04-26 4:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-25 15:26 kazumi iwane
2001-04-26 4:11 ` Lucio De Re [this message]
2001-04-25 16:19 forsyth
2001-04-26 9:51 rob pike
2003-05-11 18:17 Zoltan Jarai
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=20010426061124.A354@cackle.proxima.alt.za \
--to=lucio@proxima.alt.za \
--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).