From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] omero/olive vs rio
Date: Tue, 25 Nov 2008 13:17:11 -0500 [thread overview]
Message-ID: <f377f95cbae957c9872586241784fc73@quanstro.net> (raw)
In-Reply-To: <a560a5d00811251013y2af562b2w4903a60628f6631c@mail.gmail.com>
> Does the olive environment behave more coherently than rio? (I mean
> all --- rio, sam, acme --- have inconsistent behaviour, which makes me
> slightly uncomfortable from time to time).
> Are there any other 'window managers'? (more workspaces, eg.?)
acme is a window manager. running acme within acme is not necessary.
so saying that acme and rio are inconsistent is like complaining that gnome
running in Xnest is inconsistent within a parent kde desktop.
that being said, russ did have (at least for a time) a -a flag for p9p rio that
made rio windows behave a lot like acme. i kind of liked that.
of course, as you've noticed, this is fertile ground for new ideas.
- erik
next prev parent reply other threads:[~2008-11-25 18:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-25 18:13 Rudolf Sykora
2008-11-25 18:17 ` erik quanstrom [this message]
2008-11-25 18:24 ` Francisco J Ballesteros
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=f377f95cbae957c9872586241784fc73@quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
/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).