python-mode.el

Ipython py-execute-buffer or default-interpreter overrides window configuration

Bug #1239498 reported by deuscovrigus@gmail.com
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
python-mode.el
Fix Released
High
Andreas Roehler
python-mode.el 6.1.3 "Tarpan"

Bug Description

So I have my emacs window setup with a 3 frame setup as such , described in the example below:
http://stackoverflow.com/questions/14326568/how-can-i-force-emacs-to-use-the-bottom-window-rather-than-the-bottom-one-when-i

whenever I execute a python buffer it resets my window configuration putting the console on the bottom and source on top , deleting the second window .

Even worse, I tested with a bunch of other window configurations and everything seems to reset the configuration to source buffer on top and ipython buffer on the bottom. This behavior doesn't happen when I work with latex buffers and it only happens with python buffers.

See original description
deuscovrigus@gmail.com (deuscovrigus)
description: updated
description: updated
Andreas Roehler (a-roehler)
Changed in python-mode:
assignee: nobody → Andreas Roehler (a-roehler)
milestone: none → 6.1.3
importance: Undecided → Medium
Andreas Roehler (a-roehler)
Changed in python-mode:
importance: Medium → High
status: New → In Progress
Revision history for this message
Andreas Roehler (a-roehler) wrote :

it turns out relying on py-split-... resp. py-switch-... vars setting isn't sufficient.

Will introduce a boolean py-keep-window-configuration-p.

Remaining question: What to do if an error occurs?
Display error resp. exception buffer anyway ignoring this new var?

Revision history for this message
Andreas Roehler (a-roehler) wrote :

Please check out again, customize py-keep-windows-configuration to t

Changed in python-mode:
status: In Progress → Fix Committed
Revision history for this message
deuscovrigus@gmail.com (deuscovrigus) wrote :

I'm at branch 1343 of the python-mode branch and there is no such variable py-keep-windows-configuration.

Should I have branched the python-mode-developers instead?

Revision history for this message
Andreas Roehler (a-roehler) wrote : Re: [Bug 1239498] Re: Ipython py-execute-buffer or default-interpreter overrides window configuration

Am 23.10.2013 18:25, schrieb <email address hidden>:
> I'm at branch 1343 of the python-mode branch and there is no such
> variable py-keep-windows-configuration.
>
> Should I have branched the python-mode-developers instead?
>

Dr. Jackson thinks you may have a compiled ".elc" in your path.

See attachment.

Revision history for this message
deuscovrigus@gmail.com (deuscovrigus) wrote :

Aha! Dr. Jackson is right!
However, although my window configuration doesn't change, the first time the ipython buffer and process is created, it doesn't pop to the *Ipython* buffer and I have to do it manually.

 What I mean is, that I would like it to pop and split the window horizontally once, but subsequent calls to py-execute-buffer should not delete the windows that are on the top half of the ipython buffer. python-mode 6.1.1 had the correct behavior

Revision history for this message
Andreas Roehler (a-roehler) wrote :

Am 24.10.2013 18:58, schrieb <email address hidden>:
> Aha! Dr. Jackson is right!
> However, although my window configuration doesn't change, the first time the ipython buffer and process is created, it doesn't pop to the *Ipython* buffer and I have to do it manually.
>

Note sure IIUC, but yes, if the keep-config option is on, you have to set windows first time manually - guessing can't work than.

> What I mean is, that I would like it to pop and split the window
> horizontally once, but subsequent calls to py-execute-buffer should not
> delete the windows that are on the top half of the ipython buffer.

Implementing it probably isn't worth the price of raised complexity. At least not inside the published code.

> python-mode 6.1.1 had the correct behavior
>

Revision history for this message
deuscovrigus@gmail.com (deuscovrigus) wrote :

Aww that's too bad. Below I have python-mode 6.1.1 on my OS X and the *ipython* buffer from below will remain there without deleting the window setup in the upper half. Even if I kill the ipython buffer, invoking py-execute-buffer on any of the sources in the upper half , ipython will pop in the bottom half without deleting the windows above. Is there no way one can replicate this behavior? I really liked it due to its practicality.

Andreas Roehler (a-roehler)
Changed in python-mode:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.