Emacs opens new *Python* frame instead of using existing one

[Lars Bungum]

I am using python-mode to write python code in Emacs, and when I use the useful C-c C-c key combination to interpret the buffer, Emacs always opens another window inside the window I am using.

I prefer using Emacs split in two windows (one on each physical screen) where I program in one of them and use the Python interpreter in the other. When I asked about this on news, it was indicated to me that this was likely a bug. When Emacs already has an open buffer with the Python interpreter in it, it seems right that the code should be evaluated there.

[Gennady N. Uraltsev (gennady-uraltsev)]

Dear Lars,

I cannot reproduce this behavior with the latest version. Actually I think that this bug has already been addressed some time ago:

https://bugs.launchpad.net/python-mode/+bug/822409

(To Andreas: Can you please check if this is actually a duplicate?)

Lars, you can also check the status of your py-shell-switch-buffers-on-execute variable by executing:

M-: py-shell-switch-buffers-on-execute
and seeing the output...

This variable is customizeable and should control this behavior.

All the best,
Gennady.

[Andreas Roehler (a-roehler)]

Am 31.08.2011 22:03, schrieb Gennady N. Uraltsev:
> Dear Lars,
>
> I cannot reproduce this behavior with the latest version. Actually I
> think that this bug has already been addressed some time ago:
>
> https://bugs.launchpad.net/python-mode/+bug/822409
>
> (To Andreas: Can you please check if this is actually a duplicate?)
>

Hi Gennady,

thanks being that attentive. Pondered that question already. Must dig
into relation of processes and frames a little bit before answering
this. Interesting item BTW...

Cheers,

Andreas

> Lars, you can also check the status of your py-shell-switch-buffers-on-
> execute variable by executing:
>
> M-: py-shell-switch-buffers-on-execute
> and seeing the output...
>
> This variable is customizeable and should control this behavior.
>
> All the best,
> Gennady.
>

[Andreas Roehler (a-roehler)]

Hi,

as Gennady stated already, that bug no longer exists.

Could you check out the current trunk?
Should also not exist in latest release.

Flag it to "committed" for now.

Thanks for the report,

Andreas