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

jedi:complete: force completion after stop words #117

Merged
merged 1 commit into from Jan 29, 2014

Conversation

Projects
None yet
3 participants
@immerrr
Collaborator

immerrr commented Dec 11, 2013

Here's a minimalistic test that fails for me:

import unittest

unittest.as

With point after "as" activating jedi:complete does nothing, unlike auto-complete which initiates completion successfully. Apparently "as" is considered a stop-word after which completion is usually unwanted (unless requested specifically by a command) and jedi:complete doesn't convey the fact that auto-completion is triggered by a command.

I'm by no means an expert in auto-complete internals, but the patch works for me.

@eigengrau

This comment has been minimized.

eigengrau commented Jan 29, 2014

Hm, issuing jedi:complete still does nothing after a keyword with the patch applied.

syohex added a commit that referenced this pull request Jan 29, 2014

Merge pull request #117 from immerrr/complete-after-stopwords
jedi:complete: force completion after stop words

@syohex syohex merged commit a2ca9ae into tkf:master Jan 29, 2014

1 check failed

default The Travis CI build could not complete due to an error
Details
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment