py-split-window-on-execute erratic behavior

[[e-mail]]

So i can't help but notice that the behaviour in bug #1361531and #1361535 is still confirmed with the most recent revision of 6.2.1.

just-two kills other windows , while t, splits the windows erratically. I have described it in detail in 1361535.
Is there any temporary solution other than py-keep-windows-configuration to t?

I know there has been a lot of changes but 6.1.1 seemed to have the right window splitting behavior.
Any suggestions are welcomed.

[Andreas Roehler (a-roehler)]

Commenting closed bugs might not get attention.

Either re-open a closed bug, or --in the case given-- open a new bug including description.

Copying for now:

  #9

|-------------|-----------|
| | |
| | |
|-------------------------|
| |
| |
|-------------------------|

Right now, with py-splot-window-on execute is just-two , executing a buffer in the top-left window will kill the top right window.
If py-split-window-on execute is set to t, it will split the top left vertically as such:

|-------------|-----------|
| ----------- | |
| | |
|-------------------------|
| |
| |
|-------------------------|
The py-shell buffer will be now both on the bottom wide window and on the newly split window in the top left.

;;;;;;;;

Until this is fixed you may try the following: arrange the windows as needed and customize py-keep-windows-configuration to non-nil

[Andreas Roehler (a-roehler)]

Description doesn't make sense for me. Reading:

Right now, with py-splot-window-on execute is just-two , executing a buffer in the top-left window will kill the top right window.

With 'just-two, there is no top-left, there is either top/down or left and right.