Re: [9fans] X on Plan 9

[David Rubin <dlrubin@hotmail.com>]

anothy@cosym.net wrote:
>
> //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?

Sorry, but what's "look?" BTW, Boyd, I've been using 9term on Linux for ~6
months now, and it's been good to me.
I did try to add chording to it which was a varied success. I got very very
close, but not quite there. I still have to jiggle the mouse a little to create
a "paste" event if I cut/paste in place. I gave up at that point.


> 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.

That's for sure. Sam on Linux (at least) is a lot better than Wily too, mostly
because wily takes ages to search a file loaded over the network. Sam is very
quick in this regard. I do wish there was chording in Sam, but I respect rob's
comment (earlier) that it was hard to integrate into Sam's split architecture.

> 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.

This just means we have to write more and more usable applications for plan9. No
surprise.

	david

--
FORTRAN was the language of choice
for the same reason that three-legged races are popular.
	-- Ken Thompson, "Reflections on Trusting Trust"