code buffer unexpectedly changed to "Scratch" after executing region

Bug #1407533 reported by Wenjun Qiu
6
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-switch-buffers-on-execute-p t)
(setq py-switch-buffers-on-execute-p t)
; don't split windows
(setq py-split-windows-on-execute-p nil)
; try to automagically figure out indentation
(setq py-smart-indentation t)

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.

Wenjun Qiu (wenjunq)
summary: - buffer changed to "Scratch" after execute region
+ code buffer unexpectedly changed to "Scratch" after executing region
Revision history for this message
Andreas Roehler (a-roehler) wrote : Re: [Bug 1407533] [NEW] code buffer unexpectedly changed to "Scratch" after executing region

On 05.01.2015 03:00, StellarVC wrote:
> Public bug reported:
>
> I have the following setup:
>
> ; switch to the interpreter after executing code
> (setq py-shell-switch-buffers-on-execute-p t)

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)
> ; don't split windows
> (setq py-split-windows-on-execute-p nil)
> ; try to automagically figure out indentation
> (setq py-smart-indentation t)
>
> 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

Changed in python-mode:
assignee: nobody → Andreas Roehler (a-roehler)
importance: Undecided → High
milestone: none → 6.2.1
Revision history for this message
Andreas Roehler (a-roehler) wrote :

Will close this as fixed in trunk.

Changed in python-mode:
status: New → Fix Committed
Revision history for this message
Wenjun Qiu (wenjunq) wrote : Re: [Bug 1407533] Re: code buffer unexpectedly changed to "Scratch" after executing region

Thanks!

On Tue, Jan 13, 2015 at 2:23 PM, Andreas Roehler <email address hidden>
wrote:

> Will close this as fixed in trunk.
>
> ** Changed in: python-mode
> Status: New => Fix Committed
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1407533
>
> Title:
> code buffer unexpectedly changed to "Scratch" after executing region
>
> Status in An Emacs mode for editing Python code:
> Fix Committed
>
> Bug description:
> I have the following setup:
>
> ; switch to the interpreter after executing code
> (setq py-shell-switch-buffers-on-execute-p t)
> (setq py-switch-buffers-on-execute-p t)
> ; don't split windows
> (setq py-split-windows-on-execute-p nil)
> ; try to automagically figure out indentation
> (setq py-smart-indentation t)
>
> 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.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/python-mode/+bug/1407533/+subscriptions
>

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.

Other bug subscribers

Remote bug watches

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