# Auto-completion doesn't work as my expectation in version 9.0

When I input the following line in version 8, and press Ctrl+K after Re, I can get a drop-down auto-completion list including Rectangle:

But the same input in version 9 gives me only one candidate:

and the short-cut key Ctrl+K seems not working.

Questions:

Is there any thing I missed?

How can I get a drop-down auto-completion menu with a full candidates list?

My operation system is Windows 7 64-bit.

-
same behaviour on OS X –  acl Dec 1 '12 at 3:45
@acl Would it be some kind of context sensitive feature? I can get Rectangle in Graphics[{Black, Re}]. –  Silvia Dec 1 '12 at 3:55
The completions are context sensitive, and it seems be be getting confused in this case. Prolog->Re will offer Rectangle as a completion, but not Prolog->{Re. –  Brett Champion Dec 1 '12 at 3:58
Looks like you can work around this by using Prolog->List[ instead. –  Brett Champion Dec 1 '12 at 4:42
The bug described in this question seems to be fixed with Version 9.0.1.0 –  Lev Bishop Feb 21 '13 at 19:29

Seems that you can work around this by modifying for example SyntaxInformation[Plot]={"ArgumentsPattern" -> {_, _, _}}, at the cost of having incorrect syntax highlighting.

For some reason, setting SyntaxInformation[Plot]={"ArgumentsPattern" -> {_, {_,_,_}, __}} isn't sufficient to kill the Options[Plot] pattern matching, and I haven't found a form of the pattern that gives Rectangle as an autocompletion without also messing up the highlighting.

-
+1 I didn't think the ArgumentsPattern can be relevant! –  Silvia Dec 2 '12 at 12:27

seems like a bug and should be reported to support@wolfram.com.

Noticed when I miss-spelled Plot and wrote PLot instead, the correct auto-completion came up. This tells me the context of another command before on the same line, which is Plot in this case, was confusing the Auto-complete for the next command on the same line.

One temporary solution (not perfect) is to define the options on separate lines. Now auto-complete works, since it is not distracted any more

-
I personally like the typo solution, with the CaseSensitiveCommandCompletion off :) –  Silvia Dec 2 '12 at 12:30