You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been testing our new Tab-completion capabilities and they are working great, except for a minor detail: if you write this
range(len())
then the range calltip is shown instead of the len one. This is generated by an error in find_nearest_function_call but I'm not sure how to fix it.
Besides, I would like to have the re-trigger calltip behavior associated with "Shift+Tab" instead of "Tab" (all the rest in intelligent_tab is fine). This is just for consistency with the IPython notebook in 2.0dev (I also plan to submit a PR for qtconsole to make it work there too).
From ccordoba12 on 2014-01-11T10:43:38Z
I've been testing our new Tab-completion capabilities and they are working great, except for a minor detail: if you write this
range(len())
then the range calltip is shown instead of the len one. This is generated by an error in find_nearest_function_call but I'm not sure how to fix it.
Besides, I would like to have the re-trigger calltip behavior associated with "Shift+Tab" instead of "Tab" (all the rest in intelligent_tab is fine). This is just for consistency with the IPython notebook in 2.0dev (I also plan to submit a PR for qtconsole to make it work there too).
Original issue: http://code.google.com/p/spyderlib/issues/detail?id=1692
The text was updated successfully, but these errors were encountered: