« back to all changes in this revision
Viewing changes to ToDo.org
- Committer: Andreas Roehler
- Date: 2012-12-01 18:07:20 UTC
- Revision ID: andreas.roehler@online.de-20121201180720-nk5xq6n0u99rpq8p
py-execute-buffer-python3 looks broken, lp:1085386
new booleans dealing with Python shell output directory
After checking for a remote shell, the following variables are consulted:
py-use-current-dir-when-execute-p, default t
When `t', current directory is used by Python-shell for output of `py-execute-buffer' and related commands
py-fileless-buffer-use-default-directory-p, default t
When `py-use-current-dir-when-execute-p' is non-nil and no buffer-file exists, value of `default-directory' sets current working directory of Python output shell"
py-keep-shell-dir-when-execute-p, default nil
Don't change Python shell's current working directory when sending code.
`py-execute-directory', default nil
If nothing was set so far, $VIRTUAL_ENV and $HOME are queried.
new booleans dealing with Python shell output directory
After checking for a remote shell, the following variables are consulted:
py-use-current-dir-when-execute-p, default t
When `t', current directory is used by Python-shell for output of `py-execute-buffer' and related commands
py-fileless-buffer-use-default-directory-p, default t
When `py-use-current-dir-when-execute-p' is non-nil and no buffer-file exists, value of `default-directory' sets current working directory of Python output shell"
py-keep-shell-dir-when-execute-p, default nil
Don't change Python shell's current working directory when sending code.
`py-execute-directory', default nil
If nothing was set so far, $VIRTUAL_ENV and $HOME are queried.
added
removed
ToDo.org
