Re: [9fans] interesting potential targets for plan 9 and/or inferno

[lejatorn@gmail.com]

Honestly, I happen to boot plan9 from times to times, when I find enough
time to play with it and try to get to know it, and so far rio has not
been the major  problem for me. After all, once a term is opened, I
don't really have much more to ask from the window managing system when
it comes to getting to know the system underneath.

I'm more slowed down by:
-obviously the fact that it's quite a different system from unix,
-the fact I find the documentation unreadable in a term so I have to
read the docs in a browser on my other comp, 
-the lack of completion with tab (I know it can be done with another
key, but it's hard to break the tab habit), 
-and last but not least, getting used to edit with sam or acme 
(which of course means using the mouse) while I'm working all day with
vim without ever using the mouse.

At least now rio is starting with a dvorak keymap, otherwise it would
have been a no go :)

Cheers,
Mathieu.

On Mon, Mar 12, 2007 at 04:45:44AM -0400, Dave Eckhardt wrote:
> > I'm really with Minnich on this one. The GUI is what *everyone*
> > complains about and it's always the *first* thing they complain
> > about.  I deal with pretty intelligent people in the security
> > community and they can't handle Rio and don't want to.
> 
> In response, a serious, non-flame, question:  what's the realistic
> alternative?  It would be possible, if arduous, to replace rio with
> a clone of, say, fvwm.  But what about fluxbox and icewm and sawfish
> and windowmaker and enlightenment?  Is "the problem" really rio per
> se, or is the problem that for each person rio isn't the thing they
> already use?
> 
> I guess my question translates into "Is there *one* X window manager
> which, if cloned for Plan 9, would solve the 'rio problem'?".
> 
> Dave Eckhardt
> 
> P.S. And I guess the follow-on question is "Would that window manager
> be sufficient, or are bash and turning vt into xterm necessary too?".

-- 
GPG key on subkeys.pgp.net:

KeyID:	| Fingerprint:
683DE5F3 | 4324 5818 39AA 9545 95C6 09AF B0A4 DFEA 683D E5F3
--