Turn FuzzyAutocomplete on/off by language

[jshier]

I'd like the ability to deactivate FA for Swift files, though I can see a use for being able to turn it on/off by language in general.

[slazyk]

Such an option might be useful indeed, I already wanted to disable it for non-code files etc. I will think about it for the next update. A PR is welcome too ofc.

Side question: Why do you want it disabled in Swift files? Do you experience any problems? Is it too slow? Not useful? Or maybe something is missing? Annoying?

It might be worth it to try to eliminate the problem as well, if there is any.

[jshier]

For a few reasons:

1. I'd to see what the default autocomplete looks like for Swift files so I can files bugs with Apple.
2. It is slow. Most likely because of the sheer amount of symbols visible in a Swift file with import UIKit at the top.
3. For closures in Swift, the current autocompletion doesn't fill in the captured variable names like it does when using blocks. Having FA active in this scenario makes it slower to manually enter the variable names I want, since FA is constantly trying guess something for me with zero context

I know I can turn it off and on manually but that's a pain, even more so for a project with Objective-C and Swift.

[danielyoung11]

thanks for your Info…..hope you will update the news

在 2014年8月11日，上午5:51，Jon Shier [email protected] 写道：

For a few reasons:

1. I'd to see what the default autocomplete looks like for Swift files so I can files bugs with Apple.
2. It is slow. Most likely because of the sheer amount of symbols visible in a Swift file with import UIKit at the top.
3. For closures in Swift, the current autocompletion doesn't fill in the captured variable names like it does when using blocks. Having FA active in this scenario makes it slower to manually enter the variable names I want, since FA is constantly trying guess something for me with zero context

I know I can turn it off and on manually but that's a pain, even more so for a project with Objective-C and Swift.

—
Reply to this email directly or view it on GitHub.

[KittenYang]

Do u guys know what's the problem?