Skip to content
This repository was archived by the owner on Dec 15, 2022. It is now read-only.
This repository was archived by the owner on Dec 15, 2022. It is now read-only.

Every autocomplete-plus provider covers up snippets in the same scope for the same keyword #86

@ehteqx

Description

@ehteqx

Prerequisites

Description

When editing files that fall into a given scope for language/grammar/snippets and an autocomplete-plus provider, both active, suggestions from the autocomplete-plus provider triggered by/for the same entry as the snippet cover the snippet one(s).

After the autocomplete-plus provider completion has been inserted, in the particular case the autocomplete-plus suggestion is a "key" suggestion (thus still triggering the snippet not shown), the tab key is pressed (or whichever is bound to snippet completion), the snippet is inserted and works as expected.

Steps to Reproduce

  1. Edit a file with an active syntax highlighting for which both autocomplete-plus provider and snippets exist and are activated;
  2. Start typing a word that should trigger a snippet and that triggers also an autocomplete-plus suggestion.

Expected behavior:
In the autocomplete list shown, both the snippet and the autocomplete-plus suggestions should be shown as separate items, ordered according to a user-given priority (snippets vs. autocomplete-plus).
The user should be able to insert with the key of choice either of them.

Actual behavior:
Only the autocomplete-plus suggestion is shown.
If the insertion of the autocomplete-plus suggestion still triggers the snippet one, the latter is not shown in a list, but if no other suggestions are shown, a tab enters the snippet.

Reproduces how often: 100% for cases that fall in those described above.

Versions

OS: Ubuntu 16.04 fully updated
Install method: Official DEB package from https://atom.io/

  • Output of atom --version :
Atom    : 1.19.1
Electron: 1.6.9
Chrome  : 56.0.2924.87
Node    : 7.4.0
  • Output of apm --version :
apm  1.18.4
npm  3.10.10
node 6.9.5 x64
python 2.7.13
git 2.14.1

Addendum

I know that the issue might be duplicated, and I know that various issues have been already opened in many different repositories. However, I just wanted to be sure this specific-case issue was/is known and to describe it properly for eventual reference to others.

Thank you in advance for your support!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions