unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Pascal Bourguignon <spam@mouse-potato.com>
Subject: Re: New balance-windows
Date: Sun, 07 Aug 2005 22:42:31 +0200	[thread overview]
Message-ID: <878xzdtr60.fsf@thalassa.informatimago.com> (raw)
In-Reply-To: mailman.2899.1123441421.20277.help-gnu-emacs@gnu.org

Lennart Borgman <lennart.borgman.073@student.lu.se> writes:

> Pascal Bourguignon wrote:
>
>>>>File: elisp,  Node: Window Internals
>>>>
>>>>      
>>>>
>>>Thanks, I did not know this was available. Then the windows in each
>>>frame can be seen as a tree using those fields you mentioned. But what
>>>should then be done with this? What should the mapping between this
>>>tree and the visual view be? It looks to me that the level in the tree
>>>alone will not give any useful hint. The topology (ie whether the
>>>splitting was horizontal or vertical) must be taken into account, but
>>>maybe the level in the tree can be used too? It actually looks a bit
>>>difficult...
>>>    
>>>
>>
>>Well, it's only available to the C programmer...
>>  
>>
> I noticed when I tried to implement the algorithm I suggested. However
> it should be possible to find the split tree with a bit of work. It
> may fail when window borders meat each like a + so to say, but maybe
> trying to change the window sizes can resolve such cases. So I was
> wrong I think. It is not absolutely necessary to have the access to
> those hchild etc.
>
> I guess you are counting the children in each sub tree (something
> similar to what I suggested though you may not have read that)? Maybe
> it should be good with some weights for a user to customize?
>
> Finding the split tree is a bit tricky to say the least. You have to
> imagine a split tree and start to pick up the windows from the leafs
> and work upwards. Maybe thinking in sets helps? There are certain
> cases where you can not know how the split tree actually was (like
> three windows above each other), but from a user perspective those are
> perhaps better handled as a node with three childs whether that is the
> case in the internal split tree or not. (Perhaps this shows that it is
> better not to use the internal split tree?)



Indeed, the + case can be distinguished enlarging one window,
                            |
getting either __|--  or -+-+-, or still +, and checking for 
                          |
changes in the other windows.

So it's possible to recover the split tree from the window list.


-- 
"You cannot really appreciate Dilbert unless you read it in the
original Klingon"

  parent reply	other threads:[~2005-08-07 20:42 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-03  0:47 Making the width of three windows equal Samuel
2005-08-03  1:01 ` Pascal Bourguignon
2005-08-03  2:13   ` Samuel
2005-08-03  3:11     ` Pascal Bourguignon
2005-08-06 11:59       ` New balance-windows (Was Re: Making the width of three windows equal) Ehud Karni
2005-08-06 13:27         ` New balance-windows Ehud Karni
     [not found]         ` <mailman.2758.1123335041.20277.help-gnu-emacs@gnu.org>
2005-08-06 16:42           ` Pascal Bourguignon
2005-08-07 17:15         ` New balance-windows (Was Re: Making the width of three windows equal) Richard M. Stallman
2005-08-08  9:27           ` Ehud Karni
2005-08-09  0:27             ` Richard M. Stallman
2005-08-10  0:05             ` New balance-windows Stefan Monnier
2005-08-10  1:48               ` Stefan Monnier
     [not found]             ` <mailman.3158.1123633927.20277.help-gnu-emacs@gnu.org>
2005-08-21  0:33               ` David Combs
     [not found]           ` <mailman.2979.1123493766.20277.help-gnu-emacs@gnu.org>
2005-08-08 17:55             ` Pascal Bourguignon
     [not found]         ` <mailman.2888.1123436059.20277.help-gnu-emacs@gnu.org>
2005-08-07 18:31           ` Pascal Bourguignon
     [not found]       ` <mailman.2754.1123329756.20277.help-gnu-emacs@gnu.org>
2005-08-06 16:39         ` Pascal Bourguignon
2005-08-06 16:58           ` Lennart Borgman
     [not found]           ` <mailman.2773.1123347813.20277.help-gnu-emacs@gnu.org>
2005-08-06 20:45             ` Pascal Bourguignon
2005-08-06 21:14               ` Lennart Borgman
     [not found]               ` <mailman.2796.1123363907.20277.help-gnu-emacs@gnu.org>
2005-08-07 18:23                 ` Pascal Bourguignon
2005-08-07 18:59                   ` Lennart Borgman
     [not found]                   ` <mailman.2899.1123441421.20277.help-gnu-emacs@gnu.org>
2005-08-07 20:42                     ` Pascal Bourguignon [this message]
2005-08-06 21:05           ` Ehud Karni
2005-08-07  2:17           ` Lennart Borgman
2005-08-08  9:36             ` Ehud Karni
2005-08-08  9:47               ` Lennart Borgman
     [not found]             ` <mailman.2988.1123495783.20277.help-gnu-emacs@gnu.org>
2005-08-08 10:18               ` David Kastrup
2005-08-08 11:18                 ` Ehud Karni
2005-08-08 12:05                   ` Lennart Borgman
     [not found]                 ` <mailman.3002.1123500982.20277.help-gnu-emacs@gnu.org>
2005-08-08 18:11                   ` Pascal Bourguignon

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=878xzdtr60.fsf@thalassa.informatimago.com \
    --to=spam@mouse-potato.com \
    /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).