Comment 2 for bug 1073986

On Thu, 01 Nov 2012, Andreas Roehler wrote:
> > 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.

agree! are focus and switching the same? ;)

> 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

Once again, if I

py-shell-switch-buffers-on-execute: t

it first switches current buffer to the shell (thus maintaining
original focus). I expected it to shift focus to the Shell buffer
(already visible) instead of getting two vies of the same shell buffer.

demo:

before I press C-c C-c:
http://www.onerussian.com/tmp/gkrellShoot_11-01-12_145038.png

after:
http://www.onerussian.com/tmp/gkrellShoot_11-01-12_145054.png

with focus being in the first buffer in both of the figures, while
desired behavior to have first image with focus shifted to the shell

--
Yaroslav O. Halchenko
Postdoctoral Fellow, Department of Psychological and Brain Sciences
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419
WWW: http://www.linkedin.com/in/yarik