Comment 4 for bug 1018996

> please give some details on situation
let's try

> starting from windows splitted/not-splitted script buffer or not etc.
> diffs expectation/happening

I will expand with my expections on what I previously written:

- if I disable splitting and shell-switch-buffers-on-execute is off -- it would maximize code buffer thus hiding all other visible before

IMHO it should do NOTHING with windows/focus -- since I did not ask it to split, nor I asked it to focus. It just should send content to the shell

- 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

IMHO if split is off, there should be no additional splitting/closing of windows done -- it needs to focus (since focus is on) into the shell... if that one is not visisble -- it must be made visible instead of current (code) buffer.... makes sense?

- 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 window is already splitted, should py-shell split again?

if there is shell window already visible -- it should NOT alter anything in the state of split windows regardless either it was *-split*=on or off. if shell is not visible and "split" is on -- split to get shell window visible (but do not close other split windows). if shell is not visible and split is off -- do not split and do not in general do anything to the state of current windows splitting (only possibly switch to the shell buffer if switch is on within current code buffer split)... seems to be logical