martin rudalics <rudalics@gmx.at> writes:

>> I don't fully understnad why this is happening.  iiuc, the purpose of
>> checking for previous split is to see if the (cons window parent) refer
>> split has already happened, to avoid doing it again.  Instead of doing
>> this, I just use a vriable called `n-set' which determines if the
>> parent
>> window has already been split with the cons refer argument, so I don't
>> belive this is neccasary.
>
> I think my code is over-engineered in this regard.  Fact is that you
> create a new parent window where you should use the existing one.

I think your code was fine, my code just does same thing but instead of
storing the name of the prev window, it just stores bool if it has
previous window.

>> Nice, can you send the whole diff.
>
> Attached.  It's a bit more than that and comes without warranty.  The
> elisp manual has not been updated in this regard.

Ok so I got the thing to work under the split you described and and a
coupla other splits, and it works fine now.  I'll have a look at getting
things to work with the other diff, but iiuc I should only need
combinations (or worst case scinario is window paremater to check if it
is atom window, but iiuc this should be preventable as if it is, they I
will iterate windows when still alive, and replace the windows with
their `window-atom-root').  Also have a look at the cycle-window
command, wdyt?

Sorry for the late reply, the temprature where I live dropped to 20C
(maybe this was the reason, but I've heard rumors that an overuse of M-x
edebug-defun can causes sickness), and I got the headachy kind of ill.