Am 25.11.2012 18:39, schrieb Barry Warsaw:
> On Nov 25, 2012, at 03:21 PM, Andreas Roehler wrote:
>
>> do you get this still?
>>
>> The last remaining major issue before release 6.1.0 AFAIS.
>
> Yes, it still happens.
>
> Tracing py-shell-manage-windows, I end up in this section:
>
> (if (< (count-windows) py-max-split-windows)
> (progn
> (funcall py-split-windows-on-execute-function)
> (display-buffer py-buffer-name 'display-buffer-reuse-window))
> (display-buffer py-buffer-name 'display-buffer-reuse-window)))
>
> (count-windows) -> 1
> py-max-split-windows -> 2
>
> so, it goes on to call py-split-windows-on-execute-function which is set to
> split-windows-vertically. So the window gets split, and the *Python3* buffer
> gets displayed in the lower window.
>
what is the command used before?
should not happen, if py-split-windows-on-execute-p is nil
Am 25.11.2012 18:39, schrieb Barry Warsaw: manage- windows, I end up in this section: split-windows) windows- on-execute- function) buffer- reuse-window) ) buffer- reuse-window) )) split-windows -> 2 windows- on-execute- function which is set to vertically. So the window gets split, and the *Python3* buffer
> On Nov 25, 2012, at 03:21 PM, Andreas Roehler wrote:
>
>> do you get this still?
>>
>> The last remaining major issue before release 6.1.0 AFAIS.
>
> Yes, it still happens.
>
> Tracing py-shell-
>
> (if (< (count-windows) py-max-
> (progn
> (funcall py-split-
> (display-buffer py-buffer-name 'display-
> (display-buffer py-buffer-name 'display-
>
> (count-windows) -> 1
> py-max-
>
> so, it goes on to call py-split-
> split-windows-
> gets displayed in the lower window.
>
what is the command used before?
should not happen, if py-split- windows- on-execute- p is nil