From: Russ Cox <russcox@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] Mouse chord patch for Unix sam
Date: Wed, 16 Feb 2005 18:30:13 -0500 [thread overview]
Message-ID: <ee9e417a05021615307711fd4e@mail.gmail.com> (raw)
In-Reply-To: <FABFCC19620C1C4E87A38198E3E29C7501EC1CB4@NTKYC900PEX1.ubsgs.ubsgroup.net>
> I was browsing through the 9fans archives and came across this mail
> (http://lists.cse.psu.edu/archives/9fans/2002-April/016954.html)
> which mentions a patch for the unix sam which introduces chords
> for cut/paste. Is this still available somewhere?
there is a copy on sources in /n/sources/steve, and there
is a newer and perhaps safer version in the plan9port copy
of samterm:
http://swtch.com/usr/local/plan9/src/cmd/samterm/main.c.
they're disabled because they make sam to lock up
occasionally and it just hasn't been a high priority to
figure out why.
look for "chording".
russ
next prev parent reply other threads:[~2005-02-16 23:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-16 23:11 Noel.Hunt
2005-02-16 23:30 ` Russ Cox [this message]
2005-02-17 11:22 ` Steve Simon
2005-02-17 1:14 Noel.Hunt
2005-02-17 10:41 ` Tiit Lankots
2005-02-17 14:10 ` boyd, rounin
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=ee9e417a05021615307711fd4e@mail.gmail.com \
--to=russcox@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).