Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Minor problem with the new Tab completion functionality #1692

Closed
spyder-bot opened this issue Feb 17, 2015 · 1 comment
Closed

Minor problem with the new Tab completion functionality #1692

spyder-bot opened this issue Feb 17, 2015 · 1 comment

Comments

@spyder-bot
Copy link
Collaborator

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

@spyder-bot
Copy link
Collaborator Author

From ccordoba12 on 2014-01-13T18:55:18Z

This issue was updated by revision 69ed23217e6f .

  • Also move re-trigger calltip behavior to Shift+Tab instead of Tab to
    follow the IPython notebook behavior in 2.0dev.

Status: Fixed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant