Comment 26 for bug 1361535
Revision history for this message
| Andreas Roehler (a-roehler) wrote Re: [Bug 1361535] Re: py-switch-buffers-on-execute-p is broken. It uses/kills other buffers. | #26 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
Am 23.07.2015 um 20:27 schrieb <email address hidden>:
> The compile command does not kill all the other windows as 'just-two does.
> It simply puts the buffer in the bottom window afais, for 3 or more windows
> open. the 'just-two behavior will kill all the other windows if 3 or more
> are open.
> py-keep-windows configuration is what I've been using but then I have to
> manually bring up the Python shell buffer in the window that I want, then
> move to the end of the buffer to see the last output, then switch back to
> my source buffer. That's when I went to py-split-
> has the bad behavior of splitting windows whenever the python shell is not
> visible in any of the windows.
>
> Ideally, I would like the behavior of just-two where the python shell
> buffer is placed in the bottom window even when it's not visible, BUT not
> kill all the remaining windows if 3 or more are open. Is this possible? I
> know 6.1.1 had this behavior and was happy with it but completion would not
> really work well there.
>
>
Maybe a threshold, where instead of further split something like
other-buffer is used.