AngularJS-Sublime took over all autocompletions?

[gkatsanos]

Is this possible? (I created a custom sublime-completions file for HTML entities for example and & doesn't trigger them even though I removed it from the word separators characters, also SublimeCODEIntel doesn't work, Emmet..)
How can we remedy that situation?
Many thanks

[gkatsanos]

Anyone? This is quite blocking guys..

[subhaze]

I've not experienced any issues with this plug-in taking over autocompletions. Are there any settings you've added that might be causing this?

[gkatsanos]

Usually when I type in HTML documents I get initially the Sublime Code Intel suggestions, but I think Angular suggestions/completions are taking over. I'll console log maybe and see?

[subhaze]

That would be helpful, also, giving an exact example of:

1. What you're typing.
2. What is output.
3. What you expected.

[josip]

Same here, I have installed the plugin (no extra config) and all of it's autocompletion is working fine but I don't get "local" auto-suggest thingy anymore, ex:

Sublime Text would usually autosuggest navigationWarningMessage at this position. Pressing Control+Space says 'No available completion'. This blows big time.

With all completions disabled:

[kmkr]

I'm having the same symptoms. ST3 build 3065. Have to disable completions in this plugin to enable the other autocompletions.

[subhaze]

There's no flags passed back to ST to block other completions and I normally have Tern.js running so haven't noticed this. I'll have to dig more into this...

[subhaze]

I've had sometime to address some other issues, however, this one I'm still not able to replicate. I've turned tern_for_sublime off so I'm just relying on this plugin for completions and get the plugin completions when relevant and ST's normal completions. I'm wondering if there's some other plugin clashing with this one...

I'm always running the latest dev build of ST on OS X, build 3070 currently.

[lamogura]

@subhaze I'm using latest 3080 build and tried the code as you showed because I am having the same issue. If I "Disable JS Completions" in the package settings then it goes back to working, but otherwise is blocking local file variable names from auto complete. In case it is useful, here are my installed packages:

    "Alignment",
    "AngularJS",
    "Babel",
    "Better CoffeeScript",
    "BracketHighlighter",
    "Emmet",
    "Git",
    "GitGutter",
    "Package Control",
    "Package Syncing",
    "PackageResourceViewer",
    "ScopeHunter",
    "SublimeLinter",
    "SublimeLinter-coffeelint",
    "SublimeLinter-contrib-standard",
    "Theme - Afterglow"

[ghost]

Same problem. Show Completions includes buffer words, but the autocomplete does not. Perhaps a bug with the AngularJS package, not folding them in even at the lowest priority? I'm going to try Tern, Better Complete, etc. I want to keep the package, but I NEED my defined variables and functions to show.

[ghost]

I installed TernJS package which appears to be one solution.

[alexilyaev]

TernJS package helps here, but I think this issue should be fixed.
Having the same issue when working with sublime-jasmine package, not showing local autocompletion until I remove the AngularJS package.

[subhaze]

I'm thinking this may be an issue with completions that have $ within them... the issue is sporadic with me. I'll try digging through some more, but I've the plugin setup to pass a flag to not hide other completions :/

[ericbiewener]

I was having the same issue with the JavasciptNext package until disabling this one.

[subhaze]

Is the project you're working on available on github for me to test on? This definitely appears to be an issue, but I've been unsuccessful replicating it consistently. I've had my completions go out before but restarting sublime resolved it.

Also, is this ST 2 or 3?

[jitendersandhu]

I am having the same issue here. ST 3 Build 3141. After disabling AngularJS autocomplete, it works fine.
@subhaze - Did you get a chance to look at this. Would be great if we can use both autocompletes. Thanks!

[mmacgibbon]

Just started noticing this issue myself. About 2 weeks ago. I cant imagine what i did two weeks ago, asit was working previously. Has anyone had any updates on this?