Show More
@@ -31,6 +31,12 b'' | |||
|
31 | 31 | ;; To start an interactive ipython session run `py-shell' with ``M-x py-shell`` |
|
32 | 32 | ;; (or the default keybinding ``C-c C-!``). |
|
33 | 33 | ;; |
|
34 | ;; You can customize the arguments passed to the IPython instance at startup by | |
|
35 | ;; setting the ``py-python-command-args`` variable. For example, to start | |
|
36 | ;; always in ``pylab`` mode with hardcoded light-background colors, you can use: | |
|
37 | ;; (setq py-python-command-args '("-pylab" "-colors" "LightBG")) | |
|
38 | ;; | |
|
39 | ;; | |
|
34 | 40 | ;; NOTE: This mode is currently somewhat alpha and although I hope that it |
|
35 | 41 | ;; will work fine for most cases, doing certain things (like the |
|
36 | 42 | ;; autocompletion and a decent scheme to switch between python interpreters) |
@@ -46,14 +52,15 b'' | |||
|
46 | 52 | ;; Hints for effective usage |
|
47 | 53 | ;; ------------------------- |
|
48 | 54 | ;; |
|
49 |
;; - IMO the best feature by far of the ipython/emacs combo is how much easier |
|
|
50 |
;; makes it to find and fix bugs thanks to the ``%pdb on |
|
|
51 |
;; it: first in the ipython to shell do ``%pdb on`` then |
|
|
52 |
;; raise an exception (FIXME nice example) |
|
|
53 | ;; inspect the live objects in each stack frames and to jump to the | |
|
54 | ;; corresponding sourcecode locations as you walk up and down the stack trace | |
|
55 | ;; (even without ``%pdb on`` you can always use ``C-c -`` (`py-up-exception') | |
|
56 | ;; to jump to the corresponding source code locations). | |
|
55 | ;; - IMO the best feature by far of the ipython/emacs combo is how much easier | |
|
56 | ;; it makes it to find and fix bugs thanks to the ``%pdb on or %debug``/ | |
|
57 | ;; pdbtrack combo. Try it: first in the ipython to shell do ``%pdb on`` then | |
|
58 | ;; do something that will raise an exception (FIXME nice example), or type | |
|
59 | ;; ``%debug`` after the exception has been raised. YOu'll be amazed at how | |
|
60 | ;; easy it is to inspect the live objects in each stack frames and to jump to | |
|
61 | ;; the corresponding sourcecode locations as you walk up and down the stack | |
|
62 | ;; trace (even without ``%pdb on`` you can always use ``C-c -`` | |
|
63 | ;; (`py-up-exception') to jump to the corresponding source code locations). | |
|
57 | 64 | ;; |
|
58 | 65 | ;; - emacs gives you much more powerful commandline editing and output searching |
|
59 | 66 | ;; capabilities than ipython-standalone -- isearch is your friend if you |
@@ -79,7 +86,7 b'' | |||
|
79 | 86 | ;; variables comes later). |
|
80 | 87 | ;; |
|
81 | 88 | ;; Please send comments and feedback to the ipython-list |
|
82 |
;; (<ipython-user@scipy. |
|
|
89 | ;; (<ipython-user@scipy.org>) where I (a.s.) or someone else will try to | |
|
83 | 90 | ;; answer them (it helps if you specify your emacs version, OS etc; |
|
84 | 91 | ;; familiarity with <http://www.catb.org/~esr/faqs/smart-questions.html> might |
|
85 | 92 | ;; speed up things further). |
General Comments 0
You need to be logged in to leave comments.
Login now