Re: Suggestion for python.el and emacs.py

[Steven Huwig]

On Mar 26, 2005, at 10:01 AM, Stefan Monnier wrote:

> > In the shell, the text wraps around to the next line, which is 
> > acceptable.
> > This is not the case for Emacs windows split vertically with C-x 3 or 
> > ECB.
>
> Try (setq truncate-partial-width-windows nil)

Thanks! That's a global setting but it's good to know about. The 
completion
issues I am seeing on OS X are much more important now that I am aware 
of
them. The following debugging was all done without my customization in
emacs.py.

> > On my system, the emacs.py rlcompleter interface works correctly and
> > outputs a string, but python.el does not successfully read this string
> > and reports "Can't find completion for "os.""
>
> Can you try to debug this?

Thank you for the help on emacs debugging. After stepping through it a
few times with various inputs, here is what I found:

With a smaller set of completions (e.g. "os.a[TAB]") all is well.

With a problem case, not only does read-from-string result in nil, but
python-send-receive results in nil as well.  When debugging
python-send-receive in the same fashion, I run into the phenomenon
where accept-process-output always times out and returns nil, even when
given input known to work. Perhaps this is a result of edebug vs.
regular execution?

I seem to recall issues with OS X and ptys; could this be one of them?


Thanks,
Steven Huwig