[IPython-user] Getting IPython working with NTEmacs
Ville M. Vainio
Mon Feb 12 09:55:47 CST 2007
Can any other ntemacs user give this a spin before I (blindly) commit
it? Yet again, I don't have access to my win32 machine during
On 2/11/07, DaveS <firstname.lastname@example.org> wrote:
> I had a few issues getting IPython working smoothly with NTEmacs so I
> thought I would share my findings.
> First of all, my setup:
> NTEmacs 21.3.1
> Python 2.5
> IPython 0.7.3
> pydb 1.20
> I made some changes to Debugger.py for both pdb and pydb
> compatibility. (diff attached)
> * add trailing space to prompts so emacs sees it. (python 2.5 case)
> * set self.prompt for pydb
> * pydb writes output to it's out stream in a least one spot (list command)
> which causes problems with colours, so I initialized stdout to Term.cout.
> This doesn't seems to cause any new problems.
> * format_stack_entry was placing the '>' carrot on every frame, which
> confused emacs, so I changed it to only place it on the current frame. (I
> think plain pdb works this way)
> * I tweaked the frame line colours to make things clearer. (this is
> subjective but I like it better)
> A couple of minor items in ipython.el
> * (setq py-pydbtrack-input-prompt... should be
> (setq pydb-pydbtrack-input-prompt
> * I modified py-traceback-line-re to ignore '>' marked stack frames.
> (setq py-traceback-line-re
> "\\(^[^\t >].+?\\.py\\).*\n +[0-9]+[^\00]*?\n-+> \\([0-9]+\\)+")
> Also one minor item. When using 'run -d' with pydb, no initial breakpoint
> gets set, so the instruction about using 'c' to start things gives a
> different result then when using pdb.
> After making these changes IPython and Emacs are working great together.
> IPython-user mailing list
Ville M. Vainio - vivainio.googlepages.com
blog=360.yahoo.com/villevainio - g[mail | talk]='vivainio'
More information about the IPython-user