From: "David Leimbach" <leimy2k@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: Re: Re: [9fans] Re: OOps.. submitted a redundant patch
Date: Thu, 20 Jul 2006 09:56:15 -0700 [thread overview]
Message-ID: <3e1162e60607200956i32890972t9b20de58ad0db65c@mail.gmail.com> (raw)
In-Reply-To: <3e1162e60607200955i4033c5b0kfcc86dbc194910a2@mail.gmail.com>
On 7/20/06, David Leimbach <leimy2k@gmail.com> wrote:
> On 7/20/06, Ronald G Minnich <rminnich@lanl.gov> wrote:
> > David Leimbach wrote:
> > > 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.
> >
> >
> > um, so, what was this patch? I lost track.
The path to mine is /n/sources/patch/winwatch-hide-unhide-toggle
> >
> > ron
> >
>
> All it does is change winwatch behavior so that if you right click a
> label for a window that's hidden, the window unhides. If the window is
> not hidden, it hides it.
>
> I'm starting to believe I don't need this functionality now... (though
> if I'm opening up other "sub-rio's" it's convenient to be able to hide
> windows as well as raise them with winwatch). I started feeling like
> it wasn't so important once I saw:
>
> /n/sources/patch/sorry/ww-hideunhide
>
> This patch was a little better than mine in terms of error checking...
> the differences are minor.
>
> Russ commented that he didn't think it was necessary to have such
> behavior in his notes and I think I'm starting to agree.
>
> Dave
>
prev parent reply other threads:[~2006-07-20 16:56 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 ` [9fans] " David Leimbach
2006-07-20 15:04 ` Ronald G Minnich
2006-07-20 16:55 ` David Leimbach
2006-07-20 16:56 ` David Leimbach [this message]
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=3e1162e60607200956i32890972t9b20de58ad0db65c@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).