From: hiro <23hiro@googlemail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Acme column layout box and buttons
Date: Mon, 27 Apr 2009 15:23:17 +0200 [thread overview]
Message-ID: <f4d8fa40904270623udd02bb5k980b3ddd85f7bdff@mail.gmail.com> (raw)
In-Reply-To: <vf2ec6xngq.ln2@news.homelinux.net>
Seems logical, but I personally never felt a need for this.
To prevent line breaks I normally end up moving the windows to an
other, bigger column...
On Mon, Apr 27, 2009 at 1:51 PM, Balwinder S Dheeman
<bsd.SANSPAM@cto.homelinux.net> wrote:
> Hello,
>
> Acme likes to place new windows itself. If you prefer to change the
> layout of a window, you only need to drag the /layout box/ at the left
> of the tag line and drop it somewhere else. The point where you drop it
> selects the column where the window is to be placed now, as well as the
> line where the window should start. You can also click the layout box to
> enlarge its window a small amount (button 1), as much as possible
> without obscuring other tag lines in the column (button 2), and to fill
> the whole column vertically (button 3). You can get your other windows
> back by clicking either button-1 or button-2 on the window layout box.
>
> That's a lot of good actions attached to all the three buttons for
> handling vertical layouts. How about adding similar actions to all the
> three buttons for managing horizontal layouts to a column /layout box/.
>
> --
> Balwinder S "bdheeman" Dheeman Registered Linux User: #229709
> Anu'z Linux@HOME (Unix Shoppe) Machines: #168573, 170593, 259192
> Chandigarh, UT, 160062, India Plan9, T2, Arch/Debian/FreeBSD/XP
> Home: http://cto.homelinux.net/~bsd/ Visit: http://counter.li.org/
>
>
prev parent reply other threads:[~2009-04-27 13:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-27 11:51 Balwinder S Dheeman
2009-04-27 12:00 ` erik quanstrom
2009-04-27 12:48 ` yy
2009-04-28 9:19 ` Balwinder S Dheeman
2009-04-27 13:23 ` hiro [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=f4d8fa40904270623udd02bb5k980b3ddd85f7bdff@mail.gmail.com \
--to=23hiro@googlemail.com \
--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).