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

tab completing matplotlib #4877

Closed
moorepants opened this Issue Jan 26, 2014 · 5 comments

Comments

Projects
None yet
6 participants
@moorepants

Now that there is %matplotlib magic, I miss being able to tab complete on matplotlib.

In [2]: import matplotlib

In [3]: matplo
%matplotlib  matplotlib   

In [3]: matplot
%matplotlib  matplotlib   

In [3]: matplotl
%matplotlib  matplotlib   

In [3]: matplotli
%matplotlib  matplotlib   

In [3]: matplotlib
%matplotlib  matplotlib   

Should magics try to tab complete if you happen to have a variable in the name space that is the same name as a magic?

@Carreau

This comment has been minimized.

Show comment
Hide comment
@Carreau

Carreau Jan 26, 2014

Member

Seem legitimate as we have some code to deal with that in notebook at least.

Member

Carreau commented Jan 26, 2014

Seem legitimate as we have some code to deal with that in notebook at least.

@evectant

This comment has been minimized.

Show comment
Hide comment
@evectant

evectant May 11, 2017

Contributor

@Carreau I can submit a PR for this, but I see that test_completer:test_magic_completion_order pins down that behavior specifically:

# After the import, there should be two options, ordered like this:
text, matches = c.complete('mat')
nt.assert_equal(matches, ["matplotlib", "%matplotlib"])
Contributor

evectant commented May 11, 2017

@Carreau I can submit a PR for this, but I see that test_completer:test_magic_completion_order pins down that behavior specifically:

# After the import, there should be two options, ordered like this:
text, matches = c.complete('mat')
nt.assert_equal(matches, ["matplotlib", "%matplotlib"])
@Carreau

This comment has been minimized.

Show comment
Hide comment
@Carreau

Carreau May 11, 2017

Member

I don't think it is still that much of an issue with prompt-toolkit. We can change the test if we have a better behavior, they are not fixed in stone.

mpl

But PR welcome of course.

Member

Carreau commented May 11, 2017

I don't think it is still that much of an issue with prompt-toolkit. We can change the test if we have a better behavior, they are not fixed in stone.

mpl

But PR welcome of course.

@srinivasreddy

This comment has been minimized.

Show comment
Hide comment
@srinivasreddy

srinivasreddy Jun 12, 2017

Contributor

Safely closed? @Carreau

Contributor

srinivasreddy commented Jun 12, 2017

Safely closed? @Carreau

@takluyver takluyver closed this Jun 12, 2017

@takluyver

This comment has been minimized.

Show comment
Hide comment
@takluyver

takluyver Jun 12, 2017

Member

Yup, thanks

Member

takluyver commented Jun 12, 2017

Yup, thanks

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