py-split-windows-on-execute-p is broken. Its outcome depends unpredictably on the python shell
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
python-mode.el |
Fix Released
|
High
|
Andreas Roehler |
Bug Description
According to the documentation py-split-
For me this is not true.
In fact the behavior depends on the py-shell used.
1)
*No* splitting of windows occurs with a single *.py file open, issuing the command C-c ! and using only this simple init.el (i.e. using IPython)
;; load path of most recent python-mode.el from bzr branch lp:python-mode
(add-to-list 'load-path "~/temporary/
(require 'python-mode)
(add-to-list 'auto-mode-alist '("\\.py$" . python-mode))
(setq-default py-shell-name "ipython")
(setq-default py-python-
(setq-default py-which-bufname "IPython")
(setq py-split-
-------
2)
In contrast to that, splitting *does* occur with a single *.py file open, issuing the command C-c ! and using only this simple init.el (i.e. using plain Python)
;; load path of most recent python-mode.el from bzr branch lp:python-mode
(add-to-list 'load-path "~/temporary/
(require 'python-mode)
(add-to-list 'auto-mode-alist '("\\.py$" . python-mode))
(setq py-split-
-------
3)
For other shells I do not know
Changed in python-mode: | |
importance: | Undecided → High |
assignee: | nobody → Andreas Roehler (a-roehler) |
milestone: | none → 6.2.0 |
Changed in python-mode: | |
status: | Fix Committed → New |
Changed in python-mode: | |
status: | New → In Progress |
Changed in python-mode: | |
status: | Fix Committed → Incomplete |
Changed in python-mode: | |
status: | Incomplete → In Progress |
Changed in python-mode: | |
milestone: | 6.2.0 → 6.2.1 |
Changed in python-mode: | |
status: | In Progress → Fix Committed |
Changed in python-mode: | |
status: | Fix Committed → Fix Released |
Does this still happen?