From: YAMANASHI Takeshi <uncover@beat.cc.titech.ac.jp>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] oneko for rio
Date: Fri, 27 Apr 2001 16:28:55 +0900 [thread overview]
Message-ID: <9022.988356535@beat.cc.titech.ac.jp> (raw)
In-Reply-To: Your message of "Thu, 26 Apr 2001 15:19:45 +0200." <008801c0ce53$90097440$e8b7c6d4@SOMA>
> i had an idea to get oneko to run rio or namespace
> trikery to get the mouse events and then pass them
> on to rio.
Ok. I will start with `pipefile' and `tee'-like program
to provide /dev/^(mouse mouse2). Thank you.
--
YAMANASHI Takeshi
next prev parent reply other threads:[~2001-04-27 7:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-26 9:57 rob pike
2001-04-26 13:19 ` Boyd Roberts
2001-04-27 7:28 ` YAMANASHI Takeshi [this message]
2001-04-27 9:10 ` Douglas A. Gwyn
-- strict thread matches above, loose matches on Subject: below --
2001-05-07 8:25 okamoto
2001-04-27 13:42 rob pike
2001-04-27 16:32 ` Douglas A. Gwyn
2001-05-07 7:05 ` YAMANASHI Takeshi
2001-04-26 10:02 rog
2001-04-26 8:30 YAMANASHI Takeshi
2001-04-26 9:28 ` Boyd Roberts
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=9022.988356535@beat.cc.titech.ac.jp \
--to=uncover@beat.cc.titech.ac.jp \
--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).