Auto completion inconsistency

[ghost]

@lkdvc commented on Aug 24, 2018, 3:01 PM UTC:

Prerequisites

• Put an X between the brackets on this line if you have done all of the following:
  • Reproduced the problem in Safe Mode: https://flight-manual.atom.io/hacking-atom/sections/debugging/#using-safe-mode
  • Followed all applicable steps in the debugging guide: https://flight-manual.atom.io/hacking-atom/sections/debugging/
  • Checked the FAQs on the message board for common solutions: https://discuss.atom.io/c/faq
  • Checked that your issue isn't already filed: https://github.com/issues?utf8=✓&q=is%3Aissue+user%3Aatom
  • Checked that there is not already an Atom package that provides the described functionality: https://atom.io/packages

Description

Hey, over the past few years with Atom I've always discovered this bug but never eally had the motivation to do something about it. In the past few weeks I tried to fix it but havent really found a solution so I mad a gif and wanted to show you.

Basically im writing my code like usual, for example I write dis, then I press enter so Atom auto completes it to display: then I write for example fl for flex behind it.

But this does not always work. >>>

In the given example you can see that with justify-content it does not autocomplete the space-between, it just brings me to a new line.
Note that this is not an issue with justify-content itself, this also happens with color, display, or whatever.
If you write continously code it is really annoying.
Someone had similiar issues?
My mates who also use Atom at least have this issue as well. We usually always use enter to autocomplete the code, not tab.

We couldn't reproduce it in safe mode.

Reproduces how often: About 60% to 70% of the time.

Versions

Atom : 1.29.0
Electron: 2.0.5
Chrome : 61.0.3163.100
Node : 8.9.3

apm 1.19.0
npm 3.10.10
node 6.9.5 x64
atom 1.29.0
python
git 2.18.0.windows.1
visual studio 2015

Built-in

├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
└── [email protected]

Community

├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
└── [email protected]

Additional Information

Any additional information, configuration or data that might be necessary to reproduce the issue.

This issue was moved by rsese from atom/atom#17921.

[rsese]

Ahh sorry I missed this part initially @lkdvc:

We couldn't reproduce it in safe mode.

Since this doesn't reproduce in safe mode, it's likely that a community package is causing the issue. It may be that there is still a bug in Atom but if so, we'll need the maintainer of the package that is causing the problem to help track that down. You should file this issue on their repository so they can either fix the problem or tell us where the problem is coming from.

To figure out which package is causing the issue, you can disable all community packages and enable them one-by-one until you see the behavior again or you could try package-cop which some people have found helpful. Once you've determined what package is causing the problem, The Atom FAQ has information on how to contact the maintainers of any Atom community package or theme so you can file this issue there.

[robhuska]

I have this issue as well. I see that it was moved to the specific Linter package, but I have a different linter and I have the exact same results as the OP.

See here: AtomLinter/linter-sass-lint#206

And here: steelbrain/linter#1590 (comment)

[robhuska]

My apologies, I now realize that the two links are related... One is the main package and the other is an extension for that package. Though Linter was disabled in my packages but the extension was not, so I am not sure if the linter was even working now... Either way Linting and Autocomplete are clashing.