From: "David Leimbach" <leimy2k@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: [9fans] Re: OOps.. submitted a redundant patch
Date: Wed, 19 Jul 2006 18:03:25 -0700 [thread overview]
Message-ID: <3e1162e60607191803t58bb1c6an92ebed70f10cf9ab@mail.gmail.com> (raw)
In-Reply-To: <3e1162e60607191757n6d9986b5ra60ef46e8245ce4c@mail.gmail.com>
I did find one situation where hiding is useful... and that's when
I've taken up all of my root rio's desktop space with this sidebar
strip, and want to quickly hide winwatch itself.
*shrug*
I'll probably snap back to the old version.
On 7/19/06, David Leimbach <leimy2k@gmail.com> wrote:
> Somehow I missed that ww was for "winwatch" :-)... D'oh!
>
> Seems someone else wanted winwatch to hide and unhide windows.
>
> it was rejected because the original interface was intended to be a
> click just like clicking in rio.
>
> However it's already making it so I don't have to go through the rio
> menu to find the window I want to unhide, it seemed logical to try to
> re-hide it if it's not the one I'm looking for.
>
> I find it useful to make winwatch a long stripe vertically and have
> several independent sub-rio sessions as "virtual desktops". However
> it occurs to me that simple raising of each session above the other is
> sufficient.
>
> Oh well... at least I tried to do something :-)
>
> Dave
>
next prev parent reply other threads:[~2006-07-20 1:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-20 0:57 [9fans] " David Leimbach
2006-07-20 1:03 ` David Leimbach [this message]
2006-07-20 15:04 ` [9fans] " Ronald G Minnich
2006-07-20 16:55 ` David Leimbach
2006-07-20 16:56 ` David Leimbach
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=3e1162e60607191803t58bb1c6an92ebed70f10cf9ab@mail.gmail.com \
--to=leimy2k@gmail.com \
--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).