Am 01.03.2014 10:45, schrieb Seong-Kook Shin:
> (continued from the previous comment)
>
> python-mode calls
>
> (py-shell-completion--get-completions "socket." ...)
>
> then, it returned
>
> ("'.join(__COMPLETOR_all_completions('''socket.'''))^M")
>
> , which was totally different from what I got from the edebug session.
>
> I guess that `py-send-string-no-output` has some timing issue. I guess
> that it did try to analyze the output before the comint buffer receives
> the candidates from the python process.
>
> Hope this will help.
>
Your guess might be right. The delay for receiving results from process is 11 miliseconds
currently, a little bit short probably.
Please change py-send-string-no-output in line with
(accept-process-output process nil 11)
into
(accept-process-output process 1)
i.e. delay of one second. You might even try a higher value.
Am 01.03.2014 10:45, schrieb Seong-Kook Shin: completion- -get-completion s "socket." ...) __COMPLETOR_ all_completions ('''socket. '''))^M" ) string- no-output` has some timing issue. I guess
> (continued from the previous comment)
>
> python-mode calls
>
> (py-shell-
>
> then, it returned
>
> ("'.join(
>
> , which was totally different from what I got from the edebug session.
>
> I guess that `py-send-
> that it did try to analyze the output before the comint buffer receives
> the candidates from the python process.
>
> Hope this will help.
>
Your guess might be right. The delay for receiving results from process is 11 miliseconds
currently, a little bit short probably.
Please change py-send- string- no-output in line with
(accept- process- output process nil 11)
into
(accept- process- output process 1)
i.e. delay of one second. You might even try a higher value.
Thanks!