Comment 5 for bug 1018996

Hi,

I too have been having a hard time with the window splitting. I was having problems trying to auto-complete and having my split windows being discarded. I have just had a bit of a dig through the code and i could find the offending line but instead of the worlds lamest patch i have attached something that should be a little better.

in regards to Yaroslav's issues

- if I disable splitting and shell-switch-buffers-on-execute is off -- it would maximize code buffer thus hiding all other visible before
This should be fixed in the patch, it was the same thing that was effecting my auto-completion.

- if -focus- is on -- then it works only if I have split into 2 ... if I had more splits -- only 2 survive upon C-c C-c and it might be not the actual buffer with code sent which would be visible after C-c C-c
It will raise the window over the existing one. This is only really useful if you like working with one big window.

- If I enable splitting -- it becomes complete mad possibly making more splits, or making other splits show the buffer which I have sent with C-c C-c
If you have less than the max splits variable then it will split the current window by method of choice. otherwise it will reuse an existing window.

Does that sound reasonable?

In regards to Andreas

If window is already splitted, should py-shell split again?
I have made a max split variable, to allow the user to specify the max number of splits they prefer.

 I'm happy to change the patch if you have any feedback :)

Thanks,
Russell