inconvinient py-shell-switch-buffers-on-execute when the buffer with interpreter is already visible
Bug #1073986 reported by
Yaroslav Halchenko
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
python-mode.el |
Fix Released
|
Medium
|
Andreas Roehler |
Bug Description
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. 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 (I think that is how it was with old python-mode iirc)
Changed in python-mode: | |
assignee: | nobody → Andreas Roehler (a-roehler) |
milestone: | none → 6.1.1 |
importance: | Undecided → Medium |
Changed in python-mode: | |
status: | New → Fix Committed |
Changed in python-mode: | |
status: | Fix Committed → In Progress |
Changed in python-mode: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
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)
>