Sublime Forum

'Enter' no longer autocompletes with ':' and ';'?

#1

Sorry I’m not quite sure exactly how to phrase this. But basically, ever since I started using sublime I’d have autocomplete on, hit enter, and ‘pos’ would become ‘position:’ [for example], or ‘abs’ would become ‘absolute;’.

However now - seemingly out of the blue - it no longer adds the colon/semicolon at the end, which is extremely frustrating since I’m used to almost never having to use these keys on my own.

Anyone experienced this or have an idea why it may be happening? Latest version of Sublime, using SCSS.

0 Likes
#2

Sublime Text has some bugs with auto completion, for example:

  1. https://github.com/SublimeTextIssues/Core/issues/156 Can’t start a snippet with special characters :
  2. https://github.com/SublimeTextIssues/Core/issues/1061 Completion triggers with characters not in [a-zA-Z0-9_-] prevent buffer completions
  3. https://github.com/SublimeTextIssues/Core/issues/819 on_query_completions fails to return custom completions when some characters are used
  4. https://github.com/SublimeTextIssues/Core/issues/140 .sublime-completions problems with triggers starting with backslash and containing curly brace
  5. https://github.com/SublimeTextIssues/Core/issues/1281 Selected completion replaces text under cursor incorrectly

You can find more in:

  1. https://github.com/SublimeTextIssues/Core/issues?utf8=✓&q=is%3Aissue+is%3Aopen+label%3A"T%3A+bug"+completion

Probably your case is one of these bugs. You could try to open a new issue on the Sublime Text GitHub issue tracker with the steps to reproduce this problem, if it does not already exists, or in the package which provides the auto completions for you.

0 Likes