9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: John Floren <john@jfloren.net>
To: 9fans@9fans.net
Subject: Re: [9fans] acme and sam - mouse suggestions?
Date: Fri, 28 Jan 2022 04:21:50 +0000	[thread overview]
Message-ID: <ESF6gTEFBMsAxDQZH5lfJLq8-mCcmJYGzh1wMzba8ZLa5_H7P8B5DzEQKviqANx7XnQ87YR7jghc9jLjD_ELDreQDeePQ6i1-XG-TBMr1qQ=@jfloren.net> (raw)
In-Reply-To: <bb030b3d-b44c-6778-8e1a-9a2815ee813a@benghancock.com>

[-- Attachment #1: Type: text/plain, Size: 1376 bytes --]

My daily mouse is a Logitech 3-button mouse plugged into a PS2-USB adapter. Obviously they're not making them anymore but I've managed to acquire a bunch over the years. It's sturdy and works fine.

https://www.ebay.com/itm/384628597228

john

-------- Original Message --------
On Jan 27, 2022, 7:48 PM, Ben Hancock wrote:

> Hi all,
> 
> Acme has become my main text editor and I'm in the market for a good
> mouse with a decent middle click (i.e. B2). If product recommendations
> aren't eschewed on the list, would fellow acme and/or sam users be
> willing to share some mice suggestions? There seem to be a real dearth
> of options that have a true middle button these days.
> 
> I'm currently using an Elecom mouse designed for use with CAD programs
> that has a true middle button, and it does a serviceable job. But it
> feels cheap and I fear it will break with much more use. I also recently
> tried a gaming mouse -- a Roccat KAIN 100 Aimo -- after reading reviews
> that its scroll wheel had a decent click. But while it's quite a nice
> mouse, the middle click requires more pressure than I'd prefer.
> 
> Many thanks in advance!
> 
> - Ben
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T49f3cceea70d2b61-Me6267ae93db353cea06eb904
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

[-- Attachment #2: Type: text/html, Size: 2546 bytes --]

  parent reply	other threads:[~2022-01-28  4:22 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 [this message]
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
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='ESF6gTEFBMsAxDQZH5lfJLq8-mCcmJYGzh1wMzba8ZLa5_H7P8B5DzEQKviqANx7XnQ87YR7jghc9jLjD_ELDreQDeePQ6i1-XG-TBMr1qQ=@jfloren.net' \
    --to=john@jfloren.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).