From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Acme 3-1 chord
Date: Mon, 17 Feb 2003 20:00:38 -0500 [thread overview]
Message-ID: <94f5719623a20dc09dcd5c34e25c5ef9@plan9.bell-labs.com> (raw)
In-Reply-To: <Pine.LNX.4.30.0302171951440.24470-100000@athena>
> Are you saying the code can't keep track of
> the order in which the buttons are pressed
> and that it only knows both buttons are
> down?
It's more subtle than that. I'm saying that my mind
can't seem to tell my fingers to do a 3-1 chord.
Half the time I try to do one, I do a 1-3 chord.
Hence when I tried to do one after getting your
email, the result was pasting, and I replied thinking
3-1 pasted.
That aside, I would expect 3-1 to mean load with
arguments. Giving it another meaning seems like
a bad idea.
Russ
next prev parent reply other threads:[~2003-02-18 1:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-18 0:45 Sam
2003-02-18 0:48 ` Russ Cox
2003-02-18 0:54 ` Sam
2003-02-18 1:00 ` Russ Cox [this message]
2003-02-18 1:05 ` Sam
2003-02-18 13:41 ` Ian Broster
2003-02-19 8:34 peter a. cejchan
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=94f5719623a20dc09dcd5c34e25c5ef9@plan9.bell-labs.com \
--to=rsc@plan9.bell-labs.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).