4

For some reason, not sure exactly since when (it wasn't always like this) but, when I want to write down NSDictionary, up to NSDi it is suggesting me NSDirectoryEnumerationSkipsSubdirectoryDescendants.

At what point designing the algorithm, which surely makes use of some NSDictionaries along the way, did the engineers at Apple think "Wow, this is really useful! I use NSDirectoryEnumerationSkipsSubdirectoryDescendants so often!"?

Is there some way to bring back some sanity to it?

manecosta
  • 8,682
  • 3
  • 26
  • 39
  • 1
    Just be thankful there's code completion at all. – Milo May 01 '14 at 22:12
  • When code completion seems to be misbehaving, it is usually because you've got an error higher up in your code. Find and fix it. – matt May 01 '14 at 22:15
  • 1
    @MiloGosnell if everyone though like that we wouldn't even have computers by now. "We already have pencil and papel to do computation! Be thankful". – manecosta May 01 '14 at 22:19
  • @matt I do experience that pretty often, but this isn't the case. It's like code completion isn't tracking my most used methods and classes, which I'm sure it was before. – manecosta May 01 '14 at 22:20
  • No, I don't believe code completion has ever had any "intelligence" about this. It does tend to start by selecting the one you most recently selected, I think. – matt May 01 '14 at 22:21

1 Answers1

5

You could give the Xcode Fuzzy Autocomplete plugin a whirl.

I recommend first installing Alcatraz, an Xcode package manager, which will allow you to easily enable and disable this plugin, not to mention discover other interesting ones.

Aky
  • 1,777
  • 1
  • 14
  • 19