code buffer unexpectedly changed to "Scratch" after executing region
Bug #1407533 reported by
Wenjun Qiu
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
python-mode.el |
Fix Released
|
High
|
Andreas Roehler |
Bug Description
I have the following setup:
; switch to the interpreter after executing code
(setq py-shell-
(setq py-switch-
; don't split windows
(setq py-split-
; try to automagically figure out indentation
(setq py-smart-
After starting ipython, the window is split into two buffers (code and ipython).
After executing region, the code buffer is switched to "Scratch", which is completely unexpected.
Executing buffer doesn't have this problem.
summary: |
- buffer changed to "Scratch" after execute region + code buffer unexpectedly changed to "Scratch" after executing region |
Changed in python-mode: | |
assignee: | nobody → Andreas Roehler (a-roehler) |
importance: | Undecided → High |
milestone: | none → 6.2.1 |
Changed in python-mode: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
On 05.01.2015 03:00, StellarVC wrote: switch- buffers- on-execute- p t)
> Public bug reported:
>
> I have the following setup:
>
> ; switch to the interpreter after executing code
> (setq py-shell-
This variable shouldn't exist, resp. will have no effect.
It was renamed onto that one below with version 6.1
> (setq py-switch- buffers- on-execute- p t) windows- on-execute- p nil) indentation t)
> ; don't split windows
> (setq py-split-
> ; try to automagically figure out indentation
> (setq py-smart-
>
> After starting ipython, the window is split into two buffers (code and
> ipython).
>
> After executing region, the code buffer is switched to "Scratch", which
> is completely unexpected.
>
> Executing buffer doesn't have this problem.
>
>
> - buffer changed to "Scratch" after execute region
> + code buffer unexpectedly changed to "Scratch" after executing region
>
Did you check with current trunk?
Thanks reporting,
Andreas