From: Sam Hopkins <s.a.hopkins@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] acme cut/paste chords
Date: Mon, 6 Feb 2006 20:07:43 -0500 [thread overview]
Message-ID: <908954150602061707s6f3ba4c0kebd20ca74d4942b0@mail.gmail.com> (raw)
In-Reply-To: <a2d238df0602061541v4eb13552pf972007ec4afdd1e@mail.gmail.com>
> i realize this is a minor point (has anyone ever used a 1d 3c 2c chord?), but
> does anyone have an opinion on the matter?
Your oddities are my helpful mechanisms.
Sam
next prev parent reply other threads:[~2006-02-07 1:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-06 23:41 Eoghan Sherry
2006-02-07 1:07 ` Sam Hopkins [this message]
2006-02-07 1:20 ` Paul Lalonde
2006-02-07 1:28 ` Russ Cox
2006-02-07 20:37 ` Eoghan Sherry
2006-02-10 19:25 ` rog
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=908954150602061707s6f3ba4c0kebd20ca74d4942b0@mail.gmail.com \
--to=s.a.hopkins@gmail.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).