Am 01.03.2012 22:57, schrieb Richard Stanton:
> Completion now works, though there's one very minor oddity. Sometimes,
> when I press TAB to complete, the completion does what it's supposed to
> do, but in addition I get a new input line, as if I'd previously pressed
> Return without any text.
>
> For example,
>
> In [2]: import numpy as np
>
> In [3]: a = np.ar[now press TAB]
>
> A completion window opens fine, but the shell window now shows
>
> In [2]: import numpy as np
>
> In [3]:
> In [4]: a = np.ar
>
> Every time I press TAB, I get another blank input line inserted before
> the current line.
>
> If I only get as far as typing "np.a" before pressing TAB, I don't get
> another input line. Minor, as I said, but odd...
>
ipython-complete also uses the ipython-process, thus incrementing the
prompt counter. Changing the py-complete-function into
py-completion-at-point should avoid this - however it completes from
common Python, ignores IPython symbols, so it's probably not the
solution yet.
Am 01.03.2012 22:57, schrieb Richard Stanton:
> Completion now works, though there's one very minor oddity. Sometimes,
> when I press TAB to complete, the completion does what it's supposed to
> do, but in addition I get a new input line, as if I'd previously pressed
> Return without any text.
>
> For example,
>
> In [2]: import numpy as np
>
> In [3]: a = np.ar[now press TAB]
>
> A completion window opens fine, but the shell window now shows
>
> In [2]: import numpy as np
>
> In [3]:
> In [4]: a = np.ar
>
> Every time I press TAB, I get another blank input line inserted before
> the current line.
>
> If I only get as far as typing "np.a" before pressing TAB, I don't get
> another input line. Minor, as I said, but odd...
>
Agree. That's known at lp:939320
ipython-complete also uses the ipython-process, thus incrementing the function into at-point should avoid this - however it completes from
prompt counter. Changing the py-complete-
py-completion-
common Python, ignores IPython symbols, so it's probably not the
solution yet.