From: Geoff Collyer <geoff@collyer.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] acme without plumbing
Date: Wed, 4 Feb 2004 01:00:51 -0800 [thread overview]
Message-ID: <d9313f8ee8cafbad717d9a47963ffbcb@collyer.net> (raw)
In-Reply-To: <020faff9158ad79c3479a3de307a4c18@granite.cias.osakafu-u.ac.jp>
I'd suggest avoiding the combination of a keystroke and a mouse-button
click, which seems to me, personally, to be an abomination. I expect
the keyboard and mouse to operate independently, and this kind of
unholy union seems like the road to emacs-ville: `okay, now type
control-meta-shift-coke-bottle-F12-button-2-eject-the-CD-drive-
dim-your-monitor'.
Why not buy one of those mice with the five buttons and two wheels and
assign button 4 as `open directly in acme, bypassing plumbing' or
something?
next prev parent reply other threads:[~2004-02-04 9:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-04 8:15 okamoto
2004-02-04 9:00 ` Geoff Collyer [this message]
2004-02-04 9:05 ` okamoto
2004-02-04 16:52 ` Micah Stetson
2004-02-04 17:59 ` rob pike, esq.
2004-02-04 18:25 ` rog
2004-02-06 1:32 ` okamoto
2004-02-06 1:31 ` okamoto
2004-02-04 10:09 ` steve.simon
2004-02-04 8:42 YAMANASHI Takeshi
2004-02-04 8:58 ` okamoto
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=d9313f8ee8cafbad717d9a47963ffbcb@collyer.net \
--to=geoff@collyer.net \
--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).