autocomplete disables language completion

[farfromrefug]

If i enable autocomplete then it disables the completion files(.sublime-completions) for the language of the current file. Then if i disable autocomplete the completion files works again. Could you make so that both work at the same time

Thanks

[stephenfin]

I've didn't know .sublime-completions files even existed :D. As a result, this is going to be hard to fix. Could you provide examples to show how you think it should work? This could be a picture of just a more detailed descriptions of the "correct operation"?

[farfromrefug]

:D here is an example

{
    "scope": "source.js",
    "completions": [
    // misc completions
        {
            "trigger": "var",
            "contents": "var $1 = $2"
        }, {
            "trigger": "true",
            "contents": "true"
        }, {
            "trigger": "false",
            "contents": "false"
        }, {
            "trigger": "addEventListener\tfn. (js)",
            "contents": "addEventListener('${1:name}',${2:callback})"
        }, {
            "trigger": "removeEventListener\tfn. (js)",
            "contents": "removeEventListener('${1:name}',${2:callback})"
        }, {
            "trigger": "applyProperties()\tfn. (js)",
            "contents": "applyProperties(${0:props})"
        }, {
            "trigger": "fireEvent()\tfn. (js)",
            "contents": "fireEvent(${0:name},${1:event})"
        }, {
            "trigger": "bubbleParent\tprop. (js)",
            "contents": "bubbleParent"
        }, {
            "trigger": "bubbleParent = \tfn. (js)",
            "contents": "bubbleParent = ${0:bubble}"
        }, {
            "trigger": "scrollToBottom()\tfn. (js)",
            "contents": "scrollToBottom()"
        }, {
            "trigger": "scrollToTop()\tfn. (js)",
            "contents": "scrollToTop()"
        }, {
            "trigger": "add()\tfn. (js)",
            "contents": "add(${1})"
        }, {
            "trigger": "remove()\tfn. (js)",
            "contents": "remove(${1})"
        }, {
            "trigger": "createView()\tfn. (js)",
            "contents": "Ti.UI.createView({${1}})"
        }, {
            "trigger": "View()\tfn. (js)",
            "contents": "new View({${1}})"
        }, {
            "trigger": "createLabel()\tfn. (js)",
            "contents": "Ti.UI.createLabel({${1}})"
        }, {
            "trigger": "Label()\tfn. (js)",
            "contents": "new Label({${1}})"
        }, {
            "trigger": "createWindow()\tfn. (js)",
            "contents": "Ti.UI.createWindow({${1}})"
        }, {
            "trigger": "Window()\tfn. (js)",
            "contents": "new Window({${1}})"
        }, {
            "trigger": "createNavigationWindow()\tfn. (js)",
            "contents": "Ti.UI.createNavigationWindow({${1}})"
        }, {
            "trigger": "NavigationWindow()\tfn. (js)",
            "contents": "new NavigationWindow({${1}})"
        }
    ]
}

[stephenfin]

Ahhh - I get you now. This does seem like an issue. However, I rarely (read: never) use the autocomplete function of the plugin so I don't see this issue (I've barely looked at the piece of code that enables autocomplete in fact).

If this is a big enough nuisance and you're any way comfortable with Python, I'd suggest trying to fix it yourself. (If not, there's never a bad time to learn a new language. If you can't/won't, I'll try to have a look at it, but it's going to be a while :disappointed: (Too much to do, too little time)

[farfromrefug]

Don't worry i know python enough to look at this. Will give it a go when i have the time ;) thanks for looking