9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: rog@vitanuova.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] anyone else notice this expecation
Date: Thu, 17 Apr 2003 17:49:12 +0100	[thread overview]
Message-ID: <8c9532684bfcf812c7b86fd2627f2e88@vitanuova.com> (raw)
In-Reply-To: <3E9ED5FE.9000706@proweb.co.uk>

> I close the middle one expecting it to reveal more of the top window but
> instead the one at the bottom gets bigger and I have the same obscured
> view. So I close the middle one again, if there are a few windows I
> might end up doing it to them all.

this is useful if you're closing a load of windows: the tag on the
next window down the column ends up very close to the mouse when
you've deleted a window.

middle-button-click on that little square to the left of the tag is
your friend...

i do get acme window clutter all the time, and i haven't worked out a
good solution yet.  i did experiment with giving acme a "Hide" command
(with equivalent Edit 'H' command) but stalled on bugs in my
implementation and the thought that it probably wouldn't be that good
in practise.

speaking of acme enhancements, i've been running now for some time
with a version of the plumber that implements "plumbing priority"
(i.e.  most messages get sent to one app only, the one that's most
recently asked for them).  other ports can be marked broadcast (e.g.
mail message notifications).  it works fine, seems completely natural;
i haven't distributed it because as implemented you can't change a
port's broadcast status (not sure how it should work in the syntax).
if anyone's interested, let me know.

  cheers,
    rog.



  reply	other threads:[~2003-04-17 16:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-17 16:27 matt
2003-04-17 16:49 ` rog [this message]
2003-04-17 16:50   ` rsc
2003-04-17 17:20     ` rog
2003-04-18  0:36       ` okamoto
2003-04-20 19:33         ` rog
2003-04-20 19:51           ` Russ Cox
2003-04-22 11:31             ` rog
2003-04-22 13:10               ` matt

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=8c9532684bfcf812c7b86fd2627f2e88@vitanuova.com \
    --to=rog@vitanuova.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).