>> Try (setq truncate-partial-width-windows nil)
> Thanks! That's a global setting but it's good to know about.
You can set it buffer-locally.
> 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?
Yes, edebugging with things like accept-process-output is
always problematic. I generally resort to sprinkling the code with
(message "here var=%S" var).
> I seem to recall issues with OS X and ptys; could this be one of them?
Could be. Can you try to change process-connection-type to avoid the use of
ptys, and see if it helps?
Stefan
_______________________________________________
Emacs-pretest-bug mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
