From: Lars Magne Ingebrigtsen <larsi@ifi.uio.no>
Subject: New window configuration syntax
Date: 14 Dec 1995 22:56:29 +0100 [thread overview]
Message-ID: <w8szqcv2tte.fsf@surt.ifi.uio.no> (raw)
I think we'll call it `gnus-frame-configuration' this time. :-)
I don't remember who came up with the syntax, but it's pretty neat and
easy to work with:
CONFIG ::= (SPLIT ...)
SPLIT ::= (horizontal size SPLIT ...) |
(vertical size SPLIT) |
(buffer size [point])
So it's a recursive structure inside each frame. (Each SPLIT in
CONFIG is a separate frame.) *All* thinkable window configurations
are possible. (Unless you're a person who thinks the unthinkable.)
So now we have `gnus-frame-configuration', `gnus-buffer-configuration'
and `gnus-window-configuration', in order of presedence.
Uhmn... perhaps I'll just ditch `gnus-buffer-configuration'. It's
easy enough for users to translate a `gnus-buffer-configuration' into
a `gnus-frame-configuration'.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@ifi.uio.no * Lars Ingebrigtsen
reply other threads:[~1995-12-14 21:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=w8szqcv2tte.fsf@surt.ifi.uio.no \
--to=larsi@ifi.uio.no \
/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).