31

I'm running into an issue where XCode 7.3 autocomplete searches all possible constants using some kind of weird pattern matching algorithm. The result is that I practically have to spell the entire constant name before autocomplete allows me to press "enter" to select the suggestion.

How can I force XCode to do old, strict "begins with" autocomplete search algorithm?

For example, attempting to search for constant kEditTag, I would expect it to show up once I type kEd..., while currently I have to type keditta, to have the suggestion even show up in the autocomplete list, making it rather useless:

enter image description here

jscs
  • 63,694
  • 13
  • 151
  • 195
Alex Stone
  • 46,408
  • 55
  • 231
  • 407
  • checking preferences ->text editing -> completion tab may help. probably they added an option for completion types. – meth Feb 23 '16 at 19:19
  • Did you find a solution for this? – MCMatan Apr 03 '16 at 08:11
  • Still no solution, I remapped some #define constants into enumerated types – Alex Stone Apr 06 '16 at 15:35
  • 2
    New Auto-complete is so bad! for some reason container ranks higher than Starts with... Including when I am obviously typing an enum value into a typed expectation... It sill suggests crazy things. – eric Apr 11 '16 at 18:14

2 Answers2

1

Please go to XCode -> Preferences -> Text Editing and "Enable type-over completions" . This should do the trick

Praveen Kumar
  • 1,338
  • 3
  • 20
  • 31
0

When start to type write 2 or 3 character so xcode can interprete what you want in completion. use ctrl + space

Mr.Javed Multani
  • 12,549
  • 4
  • 53
  • 52