Pressing "Enter" or "Tab" to select a highlighted auto-predict suggestion causes a new line or tab to be inserted instead

[michaelkolber]

• Atom version: 1.28.2 x64
• linter-sass-lint version: 1.8.3
• Global sass-lint version (if used):
• Platform:
  • OSX
  • Windows
  • Linux
• Expected behaviour: When pressing "Enter" or "Tab" to select a highlighted auto-predict suggestion in a css value (not a property) in a .scss or .sass file, the selected auto-predict suggestion is inserted followed by a semi-colon. This is standard Atom behavior.
• Actual behaviour / issue description: A new line or tab is inserted instead of the auto-predicted suggestion. This does not occur every time, only sometimes, but repeatedly pressing enter on auto-predict selections will eventually yield this result. Disabling linter-sass-lint fixes this issue.

Steps to reproduce:

1. Inside any CSS block, try typing the beginning of a property name, such as max. Press enter to select the property name, in this case max-width.
2. Press enter again to select the highlighted property value, in this case none.
3. A new line appears instead of the suggestion being inserted.

Again, while this does not happen every time, it happens often enough that it's noticeable and that I've come to expect it whenever I type a property value.

Video of issue attached

Here: styles.scss.zip

[robhuska]

I too have this issue. Apparently it happens with other Linters as well. steelbrain/linter#1590 (comment)

[robhuska]

My apologies, I realize now that this is an extension for Linter... Thought Linter is disabled in my packages but this extension is not. So I am not sure if the Linter is even working now... Either way Linting and Autocomplete are clashing.