From: storm@cua.dk (Kim F. Storm)
Cc: help-gnu-emacs@gnu.org, Emacs Devel <emacs-devel@gnu.org>
Subject: Re: balance-windows again
Date: Fri, 16 Sep 2005 10:20:45 +0200 [thread overview]
Message-ID: <m3irx1iftu.fsf@kfs-l.imdomain.dk> (raw)
In-Reply-To: <432A6DC2.30606@student.lu.se> (Lennart Borgman's message of "Fri, 16 Sep 2005 09:01:22 +0200")
Lennart Borgman <lennart.borgman.073@student.lu.se> writes:
> Is there any possibility that access to the window split tree from
> elisp could be implemented in Emacs?
What format would you like the data to have ?
--
Kim F. Storm <storm@cua.dk> http://www.cua.dk
next prev parent reply other threads:[~2005-09-16 8:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-14 23:43 balance-windows again Lennart Borgman
2005-09-16 7:01 ` Lennart Borgman
2005-09-16 8:20 ` Kim F. Storm [this message]
2005-09-16 12:44 ` Lennart Borgman
2005-09-27 22:57 ` Kim F. Storm
2005-09-29 12:34 ` Kim F. Storm
2005-09-30 12:03 ` Lennart Borgman
-- strict thread matches above, loose matches on Subject: below --
2005-09-15 17:13 Bingham, Jay
2005-09-15 22:11 ` Lennart Borgman
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3irx1iftu.fsf@kfs-l.imdomain.dk \
--to=storm@cua.dk \
--cc=emacs-devel@gnu.org \
--cc=help-gnu-emacs@gnu.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).