Autocomplete-snippets not working for some/all scopes? 2nd

[Heiko-san]

Description

related to #83 ...
I can reproduce the issue using latest ubuntu with the deb package on https://atom.io/

PS:
Is this really what atom is all about?
I thought an editor which is highly modular would be a good idea...
but what it seems it is all about is a piece of software without any community...
At least if you are a newbe, it seems atom is a "Everyone works for himself" project...
I created issues at X different places , everyone just points you in a different location and in the end your issue is closed with "sorry not supported" ...
I really think the basic idea of atom is great and would like to learn nodejs just to provide some extentions for atom ... but it seems this is actually a waste of time ...
Sorry if this sounds hard , but 2 weeks of creating issues about this and no one did even try to help me with this. This is really frustrating. :(
Especially as I don't say that it is a bug per se ... I would bet that I'm just missing a little thing that is obvious to someone using atom for years.

[lee-dohm]

Hello @Heiko-san, thanks for reaching out.

I'm not sure what you mean by "I created issues at X different places , everyone just points you in a different location" and "2 weeks of creating issues about this". I only see these two issues opened by you in the entire Atom org, the earliest of which was opened a day ago as of this writing. Is there something that I'm missing?

We definitely do our best to help people. Yes, there are limitations to how far we go in doing that. One of those limitations is supporting the builds of Atom that other people or groups produce that have been shown in the past to cause an inordinate amount of support load. This excess support cost is specifically because of the changes that these third parties make to Atom before distributing it. It was preventing us from helping people that use official versions of Atom. So we had to make a choice and we feel it is completely reasonable to not support something that we didn't create.

Thanks for letting us know that you can reproduce this in a supported version of Atom. Leaving aside the Salt stuff (since it isn't applicable in Safe Mode), I can reproduce the problem you're describing using Atom v1.16.0 on Mac OS X 10.12.4 using the following steps:

1. Launch Atom
2. Replace the contents of snippets.cson with the text shown below
3. Open a new file using Cmd+N
4. Change the grammar to JavaScript by clicking the grammar selector and selecting JavaScript from the list of grammars
5. Type foo
6. Observe the full autocomplete-snippets interface shown
7. Open a new file using Cmd+N
8. Change the grammar to YAML by clicking the grammar selector and selecting YAML from the list of grammars
9. Type foo

Expected: Get the full autocomplete-snippets interface

Actual: Looks like we get only the default autocomplete provider

snippets.cson

'.source.yaml':
  'test entry':
    'prefix': 'foo'
    'description': 'This is a foobar snippet for yaml.'
    'descriptionMoreURL': 'https://docs.saltstack.com/en/latest/ref/states/requisites.html'
    'body': "foobarbaz"
'.source.js':
  'test entry':
    'prefix': 'foo'
    'description': 'This is a foobar snippet for js.'
    'descriptionMoreURL': 'https://docs.saltstack.com/en/latest/ref/states/requisites.html'
    'body': "foobarbaz"

[Heiko-san]

Hi, sorry maybe I was a little too frustrated by trying to find the right place for this issue , it is really hard to tell where to address issues with all that package distributions if you are new to atom. Especially since I didn't want to create non-sense bug issue for wrong packages (I considered the salt package and autocomplete-plus itself first), I tried some other ways (contact formulas etc) ... not the wisest choice retrospectively.

With default autocompleter you mean the one showing words already used in the document so far?
Since I can confirm I'm getting this one. If the document is completely empty no autocompletion is shown at all.

First I thought I would have to write a provider specific for salt (or yaml if you want to leave salt out), this was when I read about the autocomplete-snippets provider.
I thought maybe it doesn't implement descriptions etc. (I guess I got confused with the default provider at this point).
After having a look into the code I first considered the posibilty that it may be a bug.
May this simply be an issue with provider priority?

[lee-dohm]

Theoretically, all providers should win over the default provider.

[Heiko-san]

I guess you are right , disabling the built-in provider doesn't change anything.

[irvnriir]

@lee-dohm
i have the issue now, its very sad because i using snippets alot, is any way to fix it ? | When it can be fixed ?
(in .sqf (language arma atom package) i'm getting the functions, but not snippets as from the language package so from snippets file,
in snippets.cson words present in file showing as options (snip snipped do not working))

[irvnriir]

and i do have the snippets in "available" package's tab.
Heey, anyone here ?

[irvnriir]

Changed few package's settings and the problem fixed, changed them back, but the problem didn't reproduced, also got a question is it normal behaviour of the package:

?

[happycollision]

I am also experiencing this issue with YAML files. For anyone with this problem, the workaround I am using is to also add .text.plain to the snippet class and just using the grammar picker in the lower right to temporarily change the file to Plain Text while I am editing it.

YAML is pretty nice to look at even without highlighting, so it's a decent stop-gap while this issue is being addressed.