[Python-mode] py-execute-buffer and CWD
Andreas Röhler
andreas.roehler at online.de
Wed Nov 2 07:36:09 CET 2011
Am 01.11.2011 23:33, schrieb Andrea Crotti:
[ ... ]
> Another partially unrelated thing, I noticed the two following:
>
> (defun py-execute-buffer-no-switch (&optional async)
> "Like `py-execute-buffer', but ignores setting of
> `py-shell-switch-buffers-on-execute', output-buffer will being switched
> to."
>
> (defun py-execute-buffer-switch (&optional async)
> "Like `py-execute-buffer', but ignores setting of
> `py-shell-switch-buffers-on-execute', output-buffer will being switched
> to. "
>
> Which
> - are different functions but with the same docstring
> - are never called from anywhere and not bound to any keys..
> So are they useful at all maybe?
>
The first has a docu bug: must read "will _not_ being switched to"
maybe change that into: sending buffer remains current.
BTW better keep items apart, if you can...
More information about the Python-mode
mailing list