From: hiro <23hiro@gmail.com>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] acme and sam - mouse suggestions?
Date: Wed, 23 Mar 2022 00:20:15 +0100 [thread overview]
Message-ID: <CAFSF3XP6T3w3fmo=7cGK44Vv_6PPjm+XFGm5CQVQy7RL_L0RUg@mail.gmail.com> (raw)
In-Reply-To: <CABB-WO9PC0rbzHuPz5qV77PO4osr2H_H=Pg-A6g4ooeTSQp3FQ@mail.gmail.com>
a trackpoint is a 2-handed chording device. clearly it's limited, but
still better than any touchpad (when you are constrained to a laptop
on the go)
On 3/23/22, Stuart Morrow <morrow.stuart@gmail.com> wrote:
> On 01/02/2022, Ben Hancock <ben@benghancock.com> wrote:
>> as well but have yet to become adept at the trackpoint. Do you find
>> you're able to sweep lines as easily using it in acme as with a physical
>> mouse?
>
> A trackpoint isn't a real three-button mouse by Acme's standards. "A
> real three-button mouse" is something that supports one-to-one
> finger-to-button. A trackpoint is a two-button mouse with an
> additional scroll button. It's designed for Windows and OS/2.
>
> IBM-pattern mice (as in scrollpoint and original ThinkCentre) work for
> me. The side walls are slightly off from vertical, for dovetailing*
> into the thumb and outside finger. (Not relevant, but I've never seen
> it commented on.) I haven't tried anything else.
>
> Plus, trackpoint users will often accidentally type 'u', which on Plan
> 9 means you lose what's in your snarf buffer.
>
> For convenience, direct link to a picture of a "dovetail" joint:
> https://upload.wikimedia.org/wikipedia/commons/thumb/2/2f/Finished_dovetail.jpg/1920px-Finished_dovetail.jpg
> (since it seems these are named after a different animal in every
> single language)
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T49f3cceea70d2b61-M02cfae3bd125a7bf0b7e6060
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
next prev parent reply other threads:[~2022-03-22 23:20 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-28 3:48 Ben Hancock
2022-01-28 4:00 ` Rob Pike
2022-01-28 4:21 ` John Floren
2022-01-28 4:30 ` Mark van Atten
2022-01-28 4:39 ` Kurt H Maier via 9fans
2022-01-28 4:42 ` Kurt H Maier via 9fans
2022-01-28 4:47 ` Rob Pike
2022-01-28 4:53 ` umbraticus
2022-01-28 4:56 ` Kurt H Maier via 9fans
2022-01-28 4:59 ` Marius Eriksen
2022-02-02 7:02 ` David Arroyo
2022-01-28 5:05 ` Ben Hancock
2022-01-28 5:15 ` Bakul Shah
2022-01-28 5:38 ` Rob Pike
2022-01-28 6:08 ` adr
2022-01-28 7:14 ` umbraticus
2022-01-28 7:48 ` sirjofri
2022-01-28 8:04 ` adr
2022-01-28 9:33 ` David Leimbach via 9fans
2022-01-28 11:09 ` fijal
2022-01-29 1:22 ` adr
2022-01-29 11:30 ` fijal
2022-01-29 11:54 ` Steve Simon
2022-01-29 14:07 ` adr
2022-01-28 12:16 ` Kurt H Maier via 9fans
2022-01-28 12:43 ` Steve Simon
2022-01-28 14:36 ` Charles Forsyth
2022-01-28 18:31 ` Aram Hăvărneanu
2022-01-28 4:55 ` ori
2022-01-28 5:06 ` Alex Musolino
2022-01-28 20:24 ` Tony Mendoza
2022-01-29 22:33 ` Oleg Finkelshteyn
2022-02-01 4:25 ` Ben Hancock
2022-02-02 10:37 ` Oleg Finkelshteyn
2022-02-02 11:06 ` hiro
2022-03-22 20:01 ` contact
2022-03-22 23:09 ` Stuart Morrow
2022-03-22 23:20 ` hiro [this message]
2022-03-22 23:32 ` Kurt H Maier via 9fans
2022-03-23 0:00 ` Stuart Morrow
2022-03-23 0:48 ` Kurt H Maier via 9fans
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='CAFSF3XP6T3w3fmo=7cGK44Vv_6PPjm+XFGm5CQVQy7RL_L0RUg@mail.gmail.com' \
--to=23hiro@gmail.com \
--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).