Am 01.11.2012 15:56, schrieb Yaroslav Halchenko:
> Public bug reported:
>
> now it would just switch current buffer from code to an interpreter
> buffer even if interpreter buffer is already visible next to it -- kinda
> pointless.
visibility and focus are different things.
if switch is t, focus will shift
set py-shell-switch-buffers-on-execute to nil to avoid this
I thought that in such scenario (both code + interpreter
> visible) it would be useful if just focus was switched from code buffer
> to interpreter buffer
done when py-shell-switch-buffers-on-execute is t
(I think that is how it was with old python-mode
> iirc)
>
Am 01.11.2012 15:56, schrieb Yaroslav Halchenko:
> Public bug reported:
>
> now it would just switch current buffer from code to an interpreter
> buffer even if interpreter buffer is already visible next to it -- kinda
> pointless.
visibility and focus are different things.
if switch is t, focus will shift switch- buffers- on-execute to nil to avoid this
set py-shell-
I thought that in such scenario (both code + interpreter
> visible) it would be useful if just focus was switched from code buffer
> to interpreter buffer
done when py-shell- switch- buffers- on-execute is t
(I think that is how it was with old python-mode
> iirc)
>