From mboxrd@z Thu Jan  1 00:00:00 1970
From: anothy@cosym.net
To: 9fans@cse.psu.edu
Subject: Re: [9fans] X on Plan 9
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit
Message-Id: <20010419215900.07C31199F1@mail.cse.psu.edu>
Date: Thu, 19 Apr 2001 17:58:52 -0400
Topicbox-Message-UUID: 867561d0-eac9-11e9-9e20-41e7f4b1d025

//i added 'look' to it, but rob said it made
//the button 2 menu too long.

oo! i've been thinking about giving that a shot in rio. while i can
certainly understand the "keep the menu short" argument, i'd be all
to happy to dump cut, paste, and snarf from my button 2 menu (i use
chording exclusively for that). don't suppose you've given that
change a shot in rio already?

i agree the various chat protocols arn't well documented (and what
documentation there is doesn't often match reality). i'd looked at
just doing my own version for Plan 9, but got quite frustrate with
that fact very quickly. even napster's client had a better defined
protocol - i took a first pass at that, and had something that at
least headed in the right direction.

9wm and 9term are a poor substitute for rio, yes, but i like them
much more than [ftm]*wm and xterm, for example. and they're a lot
closer to their targets than wily is to its.

ideally, i'd get another machine to run Unix locally, and run these
apps on that. but cash is tight right now. dual-booting isn't an
acceptable option as it means taking down Plan 9, where i do the
overwhelming majority of my work/play.
-α.